I've recently found an issue where the Kubefirst-managed clusters only provisioned one cluster, with all the rest being marked as "provisioning".
This is because a free GitHub organisation only allows GitHub Actions on public repos. By default (not sure if this can/should be changed), the gitops and metaphor repos are private. To get around this, you need to make your gitops repo "public" and then delete the "provisioning" clusters and recreate them.
I would suggest that:
document this rough-edge. I don't think it'll be a problem with GitLab (we should check), but it is for GitHub. The docs should contain a line "if you are using a free GitHub org" and then provide the above problem/workaround
followed by either:
do a check when creating the repos - if it's a free org, make the repos "public"
provide an installer flag that allows you to create the repo as "public" or "private" (default to "private)
Code of Conduct
[X] I agree to follow this project's Code of Conduct
What type of suggestions?
Missing Information
What page is concerned?
No response
What version of the docs?
No response
What is the issue?
I've recently found an issue where the Kubefirst-managed clusters only provisioned one cluster, with all the rest being marked as "provisioning".
This is because a free GitHub organisation only allows GitHub Actions on public repos. By default (not sure if this can/should be changed), the
gitopsandmetaphorrepos are private. To get around this, you need to make yourgitopsrepo "public" and then delete the "provisioning" clusters and recreate them.I would suggest that:
Code of Conduct