[Cherry] Supply option to set the authz-webhook-config-file (#18) #20
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cherry-pick to release 1.29 from #18
Overview
In order to allow keystone authorization (or any external authorizing agent), the api-server must allow the configuration of the
authorization-webhook-config-file
.Details
These changes allow for the caller to provide independent args for both
authorization-webhook-config-file
andauthorization_modes
, but the two will be reconciled against one another:the
authorization_modes
can containWebhook
iffauthorization-webhook-config-file
is a valid non-empty file.the
authorization-webhook-config-file
will be ignored ifWebhook
isn't present inauthorization_modes
This is done to protect the api-server from not starting up in invalid configuration situations.