Skip to content

Support for Running Multiple CheCluster CRs in Different Namespaces in a Single Kubernetes Cluster ?Β #1985

Description

@PDCuong

Hi Che Operator team πŸ‘‹,

I'm trying to deploy multiple CheCluster custom resources (CRs) in different namespaces within the same Kubernetes cluster β€” for example:

  • che-cluster-a in namespace che-ns-a
  • che-cluster-b in namespace che-ns-b

Each CheCluster is intended to manage its own set of DevWorkspaces.

However, when I try to create a DevWorkspace, I receive this error:

Reconciler error	{"controller": "devworkspacerouting", "controllerGroup": "controller.devfile.io", "controllerKind": "DevWorkspaceRouting", "DevWorkspaceRouting": {"name":"routing-workspaceb9c3645802aa464b","namespace":"admin-che"}, "namespace": "admin-che", "name": "routing-workspaceb9c3645802aa464b", "reconcileID": "9bb5c8a3-a685-47e0-a30d-3ae61df331c4", "error": "workspace routing is invalid: the routing does not specify any Che manager in its configuration but there are 2 Che managers in the cluster"}

From my investigation, it appears this is related to how the annotation ConfigAnnotationCheManagerName is used to associate a DevWorkspace with the correct Che manager instance. Since there are two Che managers, the controller seems unsure how to route properly.

❓ Question

Is it currently possible to run multiple CheCluster CRs in separate namespaces, within the same cluster, and have them work independently?

If not supported yet, is there a recommended workaround or a plan to support multi-tenancy with multiple Che managers in the future?

Thanks for the awesome work on Che! πŸ™Œ

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions