Skip to content

[Feature] Separate controller namespace and CRD namespaces for KubeRay-Operator Dashboard #4013

@win5923

Description

@win5923

Search before asking

  • I had searched in the issues and found no similar feature requirement.

Description

In most multi-tenancy setups, the controller usually runs in a dedicated namespace, while CRD instances are created in different namespaces to separate tenant workloads.

Currently, the KubeRay operator dashboard filter both the controller runtime and CRDs by the same namespace. This makes it difficult to support typical multi-tenancy patterns.

Image

We can create a new parameter called ControllerNamespace for the controller runtime.

You can following this doc to set up Prometheus and Grafana

Use case

for multi-tenancy

Related issues

No response

Are you willing to submit a PR?

  • Yes I am willing to submit a PR!

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions