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
Move config v1 IP validation to CEL #1802
Conversation
Hello @JoelSpeed! Some important instructions when contributing to openshift/api: |
die regex, die! /lgtm |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: deads2k, JoelSpeed, mkowalski 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 |
@JoelSpeed: 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/test-infra repository. I understand the commands that are listed here. |
/hold Revision ae74cd4 was retested 3 times: holding |
/hold cancel Master keeps merging, not actually an issue with this PR |
/retest-required |
/label acknowledge-critical-fixes-only |
3cbbe4f
into
openshift:master
TRT-1563: Revert #1802 "Move config v1 IP validation to CEL"
…ip-cidr"" This reverts commit a8d9711.
…ip-cidr"" This reverts commit a8d9711.
…ip-cidr"" This reverts commit a8d9711.
…ip-cidr"" This reverts commit a8d9711.
Now that we have CEL validation for IP and CIDR in openshift 4.16, this PR changes to using CEL for two newly introduced APIs in 4.16/4.15.
The regex being removed attempted to support IPv4 addresses mapped in IPv6 addresses, however, the regex was broken and only actually accepted
255.255.255.255
as a valid v4 address as part of the 4in6 mapping.The new CEL explicitly forbids 4in6.
I've spoken to @mkowalski and @sadasu and we believe this change should be ok.
For both use cases, we do not support IP 4in6 addresses, this is noted in the product docs