-
Notifications
You must be signed in to change notification settings - Fork 587
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
rename webhook to be eventing-webhook to avoid potential clash #1269
Conversation
@Harwayne @evankanderson any thoughts on this PR ? |
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'll leave approval to @evankanderson.
name: config-logging | ||
|
||
--- | ||
|
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.
Add a TODO to remove in 0.8.
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.
Will there be any conflicts between the two running simultaneously?
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.
The two won't run simultaneously (at least for more than a moment), because this YAML sets replicas=0 on the old Deployment, which will probably take effect around the same time as the new Deployment is started (probably faster, but not taking a bet).
If both end up running at once, they will both register their mutating webhook, but that should be fine -- whichever one is called earlier will do the defaulting, and the other will simply validate the same data which has been validated before.
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
/approve
name: config-logging | ||
|
||
--- | ||
|
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.
The two won't run simultaneously (at least for more than a moment), because this YAML sets replicas=0 on the old Deployment, which will probably take effect around the same time as the new Deployment is started (probably faster, but not taking a bet).
If both end up running at once, they will both register their mutating webhook, but that should be fine -- whichever one is called earlier will do the defaulting, and the other will simply validate the same data which has been validated before.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: evankanderson, matzew 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 |
Fixes #1260
Proposed Changes
webhook
to beeventing-webhook
webhook
deployment, but withreplicas: 0
Release Note