-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Split apart defaulting and validation webhooks #5947
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mattmoor 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 |
e7da2f3
to
a650b1a
Compare
/retest |
5822768
to
87f8388
Compare
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.
/lgtm
I guess something stops working on downgrade... |
Good catch, I forgot downgrade was back. Yeah, so downgrade is a problem without |
87f8388
to
adb69a4
Compare
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.
Found go linting violations, please merge: mattmoor#106
The following jobs failed:
Failed non-flaky tests preventing automatic retry of pull-knative-serving-unit-tests:
|
/retest |
adb69a4
to
22d08eb
Compare
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.
Found go linting violations, please merge: mattmoor#107
/retest |
Ok, I had a chance to debug what's happening here, but I haven't figured out how to fix this yet. tl;dr Unfortunately for the downgrade test, our new reconciler-based webhook logic is far too effective. As the downgraded webhook comes up it updates the validating webhook to use If this were all, then things would be peachy, however, before we have a chance to shutdown the HEAD webhook it has already observed the change to its mutating webhook and reconciled it back to the path we use at HEAD (in this PR) which is If you wait 10 minutes (🙄) the downgrade will fix itself, since that's the interval at which it ensures the webhook is registered, but by then the downgrade test (and probe) have long since failed. If we simply wait to land this change until after the 0.11 cut, then it will effectively fix itself (for single-version downgrade), but I'd still like to see whether we can land at least parts of these changes. cc @vagababov @dgerd |
I think I have a relatively surgical tweak to get most of this merged. I'll see how gross folks (and myself) find it when I've put some lipstick on it. 🤞 |
22d08eb
to
7853d12
Compare
/retest |
7853d12
to
f2a1a50
Compare
f2a1a50
to
a091a91
Compare
@@ -136,7 +163,8 @@ func main() { | |||
|
|||
sharedmain.MainWithContext(ctx, "webhook", | |||
certificates.NewController, | |||
NewResourceAdmissionController, | |||
NewDefaultingAdmissionController, |
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.
SO AWESOME
/lgtm Thanks for finding that issue with the webhooks and fixing it. |
a091a91
to
de4814e
Compare
/lgtm |
/hold cancel |
Related: knative/pkg#848
/hold
until upstream PR lands.