You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
GitOps catalog is only available on cluster 0, which is the cluster the user create with launch up or helm install on an existing cluster. It means the catalog isn't available on the newly created cluster, and that cluster 0 needs to be alive to use the GitOps catalog: even if they deployed on the cloud, Docker Desktop need to run, and the install cluster (cluster 0) can't be destroyed.
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Which version of kubefirst are you using?
2.2.2
Which cloud provider?
None specific
Which installation type?
UI (Console app)
Which distributed Git provider?
None specific
What is the issue?
GitOps catalog is only available on cluster 0, which is the cluster the user create with
launch up
orhelm install
on an existing cluster. It means the catalog isn't available on the newly created cluster, and that cluster 0 needs to be alive to use the GitOps catalog: even if they deployed on the cloud, Docker Desktop need to run, and the install cluster (cluster 0) can't be destroyed.Code of Conduct
The text was updated successfully, but these errors were encountered: