-
Notifications
You must be signed in to change notification settings - Fork 383
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
✨ Enable webhook authorization options #3198
base: main
Are you sure you want to change the base?
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/test all |
…ing legacy-cloud-providers dependency On-behalf-of: @SAP [email protected]
/test all |
…e kcp options On-behalf-of: @SAP [email protected]
/test all |
Summary
This PR allows to configure an external webhook for authorization. Previously the relevant flags have been explicitly disabled in kcp, because kcp has its own authorizer. The webhook authorizer would sit next to the existing authorizers (allowPath, allowGroup) and so is an alternative to the built-in authorizers.
Since I only implemented and tested the webhook mode, I did not surface the
--authorization-mode
flag, but instead set this value based on the presence of the other webhook related flags.This PR also includes a dependency bump to include kcp-dev/kubernetes#151, which will take care of including the cluster name in the webhook's payload. In that dependency bump is also, slightly hidden, a cleanup for the
bump-k8s
script, which failed at least since the 1.31 bump since thelegacy-cloud-providers
module doesn't exist anymore.Lastly, I removed the custom Authentication setup logic, as what we did here was exactly the same as upstream code already does and it simply seemed redundant.
Release Notes