Skip to content
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

Merged
merged 1 commit into from
May 29, 2019

Conversation

matzew
Copy link
Member

@matzew matzew commented May 24, 2019

Fixes #1260

Proposed Changes

  • rename webhook to be eventing-webhook
  • keep old webhook deployment, but with replicas: 0

Release Note

the webhook has been renamed to eventing-webhook, and the old webhook will scale to 0

@googlebot googlebot added the cla: yes Indicates the PR's author has signed the CLA. label May 24, 2019
@knative-prow-robot knative-prow-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label May 24, 2019
@matzew
Copy link
Member Author

matzew commented May 24, 2019

@Harwayne @evankanderson any thoughts on this PR ?

Copy link
Contributor

@Harwayne Harwayne left a 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

---

Copy link
Contributor

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.

Copy link
Contributor

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?

Copy link
Member

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.

@knative-prow-robot knative-prow-robot added the lgtm Indicates that a PR is ready to be merged. label May 28, 2019
Copy link
Member

@evankanderson evankanderson left a 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

---

Copy link
Member

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.

@knative-prow-robot
Copy link
Contributor

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@knative-prow-robot knative-prow-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 29, 2019
@knative-prow-robot knative-prow-robot merged commit 1cd0885 into knative:master May 29, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cla: yes Indicates the PR's author has signed the CLA. lgtm Indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[BUG] rename webhook
6 participants