question-mark
Stuck on an issue?

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 issue

Is 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:closed
  • Created a year ago
  • Comments:8 (8 by maintainers)

github_iconTop GitHub Comments

2reactions
l0rdcommented, May 23, 2022
1reaction
l0rdcommented, May 18, 2022

A couple of comments:

  1. By default chectl creates the CheCluster CR in eclipse-che, not openshift-operators (dsc should NOT deploy to openshift-operators).

  2. OpenShift Pipelines operator automatically creates an ArgoCD Custom Resource in openshift-gitops namespace. So 1) the default is an openshift- 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

Read more comments on GitHub >

github_iconTop Results From Across the Web

Chapter 4. Configuring CodeReady Workspaces
Installing CodeReady Workspaces on OpenShift 3 using the Operator ... In that case, new namespace will be created for each user. Used by...
Read more >
CheCluster Custom Resource fields reference - Eclipse
Indicates if is allowed to automatically create a user namespace. If it set to false, then user namespace must be pre-created by a...
Read more >
Structuring your deployment - IBM
How should I deploy the IBM Cloud Pak® for Integration operators and ... workloads, and namespaces, OpenShift itself does not natively support strong ......
Read more >
v1 - Go Packages
If the value is true, then a new OpenShift OAuth user will be created for the ... Instructs the Operator on whether or...
Read more >
Eclipse Che - OperatorHub.io
When the operator is installed, create a new CR of Kind CheCluster (click the Create New button). The CR spec contains all defaults...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found