-
Notifications
You must be signed in to change notification settings - Fork 562
CNTRLPLANE-368: improve OIDC field validations for Authentication resources #2409
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
CNTRLPLANE-368: improve OIDC field validations for Authentication resources #2409
Conversation
as we discovered in openshift/kubernetes#2353 (comment) that the current constraints are to loose and result in excessive expression compile times when used up to the limitations. Signed-off-by: Bryce Palmer <[email protected]>
@everettraven: This pull request explicitly references no jira issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
Hello @everettraven! Some important instructions when contributing to openshift/api: |
This PR may evolve to include additional validation changes. /hold |
@everettraven: This pull request references CNTRLPLANE-368 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.20.0" version, but no target version was set. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
@everettraven: This pull request references CNTRLPLANE-368 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.20.0" version, but no target version was set. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are any of these fields embedded in the HostedCluster on HyperShift? I believe they may be.
If they are, we need to be careful about the changes we introduce and how they might impact the HostedCluster API on older API servers (CC @enxebre since we talked about this yesterday)
Yes, they are.
In theory, the ratcheting The tightening of the validations on the CEL expression fields should be safe because the feature-gate that corresponds to those fields is TPNU only for both HCP and OCP. |
0cc875b
to
8ef2976
Compare
to align with the KAS validations Signed-off-by: Bryce Palmer <[email protected]>
8ef2976
to
2cfc921
Compare
/hold cancel |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: everettraven, JoelSpeed The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest-required |
@everettraven: The following test failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
/retest-required |
a42cd21
into
openshift:master
[ART PR BUILD NOTIFIER] Distgit: ose-cluster-config-api |
Updates some of the validations for OIDC-specific fields in the
authentications.config.openshift.io
CRD.Specifically:
issuerURL
constraints to align with those in the KAS: https://github.com/kubernetes/kubernetes/blob/8e6d788887034b799f6c2a86991a68a080bb0576/staging/src/k8s.io/apiserver/pkg/apis/apiserver/validation/validation.go#L158-L184 - this should be safe to ratchet as specifying an invalid value means that the KAS will not successfully rollout