Organization-Dedicated Control-Plane #45

New issue

Open

opened 2025-04-09 06:48:26 +00:00 by tobru · 0 comments

tobru commented

2025-04-09 06:48:26 +00:00

Owner

Stories

As an organization, I want to have a dedicated control-plane which is not shared with other organizations.

Background

By now, we do implement the shared control-plane architecture, where organizations share the control-planes. Each organization has its own namespace on the shared control-plane where the service instances are created in.

Organizations wish to have their dedicated control-plane where they have full control over the namespaces on the cluster.

Implementation Notes

Make it possible to mark a control-plane as "dedicated" and assign it to an organization (can all happen in Django admin, no frontend required for that)
When a control-plane is marked as dedicated, it behaves differently:
- The control-plane is only visible to the organization it belongs to
- No organization namespaces are created or managed on such a control-plane
- When creating a service instance, the user has to choose in which namespace the instance should be created
- The list of available namespaces is retrieved directly from the control-plane
- A new namespace can be created directly when creating an instance
- On the service listing page, the namespace a service instance lives is displayed

## Stories _As an organization, I want to have a dedicated control-plane which is not shared with other organizations._ ### Background By now, we do implement the shared control-plane architecture, where organizations share the control-planes. Each organization has its own namespace on the shared control-plane where the service instances are created in. Organizations wish to have their dedicated control-plane where they have full control over the namespaces on the cluster. ## Implementation Notes * Make it possible to mark a control-plane as "dedicated" and assign it to an organization (can all happen in Django admin, no frontend required for that) * When a control-plane is marked as dedicated, it behaves differently: * The control-plane is only visible to the organization it belongs to * No organization namespaces are created or managed on such a control-plane * When creating a service instance, the user has to choose in which namespace the instance should be created * The list of available namespaces is retrieved directly from the control-plane * A new namespace can be created directly when creating an instance * On the service listing page, the namespace a service instance lives is displayed