KEP: Centralized Namespace Management Across ManagedClusterSets #147
Conversation
jnpacker
commented
Jul 14, 2025
jnpacker
commented
- Add support for Globally defined namespace(s) on the ManagedClusterSet
- Support RBAC via ClusterPermissions for the Globally defined namespace(s)
* Add support for Globally defined namespace(s) on the ManagedClusterSet * Support RBAC via ClusterPermissions for the Globally defined namespace(s) Signed-off-by: Joshua Packer <[email protected]>
|
|
||
| #### Story 1 | ||
| Create a Global Namespace, this namespace will be created on all Managed Clusters in a Managed Cluster Set, and | ||
| the appropriate Cluster Permissions will be applied. |
There was a problem hiding this comment.
if we create a managedclusterbinding that binds a clusterset to a namespace, does it mean we should sync the namespace that creates managedclusterbinding to all clusters? It seems we can add a spec field in managedclusterbinding to achieve that.
There was a problem hiding this comment.
That was one of two options I was thinking. Either we use the existing binding and just include a field as you mentioned or we create a new resource to track it.
The field is much less invasive, and we already have the namespace binding.
There was a problem hiding this comment.
yes, I think having a field in the managedclustersetbinding indicating "this clustersetbindings needs namespace to be synced to all managed clusters" makes sense, and it could be disabled by default which ensure the backward compatibility.
Signed-off-by: Jian Qiu <[email protected]>
Add implementation details
Signed-off-by: Jian Qiu <[email protected]>
Update API and plan
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jnpacker, qiujian16 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-merge-bot
bot
merged commit 8ccbe0f
into
open-cluster-management-io:main
2 participants
