Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GitOps catalog is only available on cluster 0 #1679

Closed
1 task done
fharper opened this issue Jul 10, 2023 · 0 comments · Fixed by #1751
Closed
1 task done

GitOps catalog is only available on cluster 0 #1679

fharper opened this issue Jul 10, 2023 · 0 comments · Fixed by #1751
Assignees
Labels
bug Something isn't working

Comments

@fharper
Copy link
Contributor

fharper commented Jul 10, 2023

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 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
@fharper fharper added the bug Something isn't working label Jul 10, 2023
@fharper fharper changed the title GitOps catalog is only available on cluster 0. GitOps catalog is only available on cluster 0 Jul 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants