Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
CheCluster CR should not be created in openshift-operators namespace
See original GitHub issueIs your enhancement related to a problem? Please describe
Che operands are deployed in openshift-operators namespace. That namespace, as it’s name suggests, is dedicated to operators and not to operands. We should not deploy postgres, database, registries, server, dashboard etc…there.
Describe the solution you’d like
CheCluster CR should be created in eclipse-che namespace as soon as the operator is deployed.
That also means that an admin doesn’t have to manually create a CheCluster after Che operator subcription: it’s automatically created (1 step installation instead of 2 steps installation).
Additional information
OpenShift GitOps operator does that: it creates the openshift-gitops namespace if it doesn’t exist and
Red Hat product OpenShift Dev Spaces default CheCluster namespace should be openshift-devspaces.
Issue Analytics
- State:
- Created a year ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Downstream issue
A couple of comments:
By default chectl creates the
CheClusterCR ineclipse-che, notopenshift-operators(dscshould NOT deploy toopenshift-operators).OpenShift Pipelines operator automatically creates an ArgoCD Custom Resource in
openshift-gitopsnamespace. So 1) the default is anopenshift-prefixed namespace 2) the CR is automatically created in one step (whereas Che requires admins to do that in 2 steps). This should be the example to follow.cc @dmytro-ndp @nickboldt @Kasturi1820 @RickJWagner