This repository was archived by the owner on Apr 17, 2025. It is now read-only.
generated from kubernetes/kubernetes-template-project
-
Notifications
You must be signed in to change notification settings - Fork 114
Default subnamespace permissions #317
Labels
lifecycle/rotten
Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Comments
Yes, I think it makes sense. Maybe add permissions to the other default aggregated cluster roles (view, admin and cluster-reader) also? |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
merged |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Each time when I install HNC I give permissions to the
clusterRole/edit
on the hnc custom resources.It allows the clients create their own sub namespaces if they have at least edit role:
So I'm wondering, should I create a PR so it would be like that by default?
The text was updated successfully, but these errors were encountered: