-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
Remove deletion of coredns deployment. #7211
Remove deletion of coredns deployment. #7211
Conversation
Hi @dlouks. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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 think you can delete the whole file |
@champtar, I believe ensuring the kube-dns service doesn't exist is still needed as kubeadm will recreate the service on upgrade if it is able to (i.e. the IP kubeadm is trying to use for the |
Why do we name our service differently ? Is it just legacy ? Can we cleanup that too ? (My opinion is to be as close to kubeadm as possible) |
kubespray create own coredns deployment in this task task in PR delete coredns created by kubeadm.
So, in principle, you can delete this task. |
@LuckySB, do you have issue with this annotation? PR updated with this annotation. |
…deployment if annotation is missing.
f23d96a
to
cce9e95
Compare
…e where it doesn't exist yet
/ok-to-test |
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.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dlouks, floryut 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 |
/lgtm |
* Add unique annotation on coredns deployment and only remove existing deployment if annotation is missing. * Ignore errors when gathering coredns deployment details to handle case where it doesn't exist yet * Remove run_once, deletegate_to and add to when statement (cherry picked from commit 0cc1726)
* Add unique annotation on coredns deployment and only remove existing deployment if annotation is missing. * Ignore errors when gathering coredns deployment details to handle case where it doesn't exist yet * Remove run_once, deletegate_to and add to when statement (cherry picked from commit 0cc1726)
* Add unique annotation on coredns deployment and only remove existing deployment if annotation is missing. * Ignore errors when gathering coredns deployment details to handle case where it doesn't exist yet * Remove run_once, deletegate_to and add to when statement
What type of PR is this?
/kind bug
What this PR does / why we need it: Deleting the coredns deployment on every run using
cluster.yml
creates a brief DNS outage. From the testing I've done on new or existing clusters it doesn't seem to matter if the coredns deployment is deleted or this task is skipped, either way the deployment ends up configured the same way. Please let me know if I'm missing something as I can't find the reason this step is required.Which issue(s) this PR fixes:
Fixes #6387
Special notes for your reviewer:
Does this PR introduce a user-facing change?: