-
Notifications
You must be signed in to change notification settings - Fork 40.6k
Should we add authorization-always-allow-groups
flag as well?
#110345
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
cc @elgnay |
/transfer kubernetes |
/sig api-machinery |
/sig auth |
/triage accepted |
Personally I think no we should not add this, can it not be configured via e.g. RBAC? |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs 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 and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
/assign @enj |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
This issue has not been updated in over 1 year, and should be re-triaged. You can:
For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/ /remove-triage accepted |
/triage accepted |
This issue has not been updated in over 1 year, and should be re-triaged. You can:
For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/ /remove-triage accepted |
Hello, team. I was using apiserver to implement my webhook server, but found these is no flag used to set
always-allow-groups
, but there is a flag to setauthorization-always-allow-paths
:https://github.com/kubernetes/apiserver/blob/ac613d389acee636c827a241b1eba448e6b15f3a/pkg/server/options/authorization.go#L157
Should we add
authorization-always-allow-groups
as well? or is there anyway for me to setAlwaysAllowGroups
?Thanks and looking forward for your reply.😁
The text was updated successfully, but these errors were encountered: