WIP: update KAS bootstrapping to get RBR from CAO #6137
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.
What this PR does / why we need it:
RoleBindingRestriction
CRD from the cluster-authentication-operator's manifest renderer if OAuth is enabled. This is needed so that the Kubernetes API server can start up successfully when theRoleBindingRestriction
CRD is no longer included in the openshift/api generated payload manifests. See CNTRLPLANE-72: remove RoleBindingRestriction CRD from payload api#2138authorization.openshift.io/RestrictSubjectBindings
andauthorization.openshift.io/ValidateRoleBindingRestrictions
admission plugins on the Kubernetes API server if the OAuth is not enabled. This was proposed in (oidc): add considerations for impacted kube-apiserver admission plugins enhancements#1726Which issue(s) this PR fixes (optional, use
fixes #<issue_number>(, fixes #<issue_number>, ...)
format, where issue_number might be a GitHub issue, or a Jira story:Fixes #
Checklist