Staging and Production clusters remain in provisioning state on a clean install

[mrsimonemms]

Which version of kubefirst are you using?

2.4.6, 2.4.10

Which cloud provider?

Civo, Google Cloud

Which DNS?

Cloud ones (default), Cloudflare

Which installation type?

CLI, Marketplace

Which distributed Git provider?

GitHub

Did you use a fork of gitops-template?

No

Which Operating System?

Linux

What is the issue?

When installing a fresh install of Kubefirst, it creates three clusters - development, staging and production. The staging and productionclusters remain inprovisioning` state forever.

Initially, I thought this was due to GitHub not allowing orgs to run private GitHub Actions (see konstructio/kubefirst-docs#720), however that appears not to be the case. Indeed, in my registry/clusters directory, the staging and production cluster do not appear.

When looking at the commit history, we only see the creation of the development cluster.

Code of Conduct

• I agree to follow this project's Code of Conduct