blocked-edges/4.6.6: Block * -> 4.6.(6|7) on born-in-4.1 ingress #577
Conversation
openshift-ci-robot
added
the
approved
There aren't all that many born-in-4.1 clusters within striking distance of 4.6.6+, so the number of vulnerable clusters is small. But *.apps breaking would be really bad, so block the edges to protect that small subset. We could keep 4.6.6 -> 4.6.7 in place, but I didn't bother to figure out the regexp for "all versions that aren't 4.6.6".
wking
force-pushed
the
block-4.6.6-on-internal-ingress
branch
from
c34920a to
9e6117a
Compare
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sdodson, wking The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
publish /retest |
|
e2e passed, I don't care enough about publish to dig in. /override ci/prow/publish |
|
@wking: Overrode contexts on behalf of wking: ci/prow/publish DetailsIn 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 kubernetes/test-infra repository. |
4 participants
There aren't all that many born-in-4.1 clusters within striking distance of 4.6.6+, so the number of vulnerable clusters is small. But
*.appsbreaking would be really bad, so block the edges to protect that small subset. rhbz#1904582.We could keep 4.6.6 -> 4.6.7 in place, but I didn't bother to figure out the regexp for "all versions that aren't 4.6.6".