You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My name is San, we met at the Kubecon yesterday and talked about the possibility of disabling namespace creation in kcp.
To give more context: I only control a pre-created namespace provisioned by the platform team in my company. Now, I would like to install CRDs, but it would require cluster wide permission. So I'm looking into solutions that can help me install CRD by ourselves, no need to involve the platform team (that will take lots of time due to many reasons).
kcp concept is great, but I can not apply for my use case because it would require talking to the platform team and ask for namespace creation permission. Those namespaces, when pre-created, actually are synced across clusters running in pre-defined regions. So we control that unique namespace for all internal k8s clusters.
So I just want to ask if we can do a 1:1 mapping, we only need 1 kcp workspace that map to 1 namespace in the physical cluster and remove the namespace creation permission? Then any resources we deploy on that workspace will be synced to the namespace. That would help me adopt the tool for my team only, then gradually introduce it to a other teams within the company.
Thanks a lot for the chat at Kubecon. I really appreciate it.
Looking forward to hearing from your feedback.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi @ncdc ,
My name is San, we met at the Kubecon yesterday and talked about the possibility of disabling namespace creation in kcp.
To give more context: I only control a pre-created namespace provisioned by the platform team in my company. Now, I would like to install CRDs, but it would require cluster wide permission. So I'm looking into solutions that can help me install CRD by ourselves, no need to involve the platform team (that will take lots of time due to many reasons).
kcp concept is great, but I can not apply for my use case because it would require talking to the platform team and ask for namespace creation permission. Those namespaces, when pre-created, actually are synced across clusters running in pre-defined regions. So we control that unique namespace for all internal k8s clusters.
So I just want to ask if we can do a 1:1 mapping, we only need 1 kcp workspace that map to 1 namespace in the physical cluster and remove the namespace creation permission? Then any resources we deploy on that workspace will be synced to the namespace. That would help me adopt the tool for my team only, then gradually introduce it to a other teams within the company.
Thanks a lot for the chat at Kubecon. I really appreciate it.
Looking forward to hearing from your feedback.
Beta Was this translation helpful? Give feedback.
All reactions