-
Notifications
You must be signed in to change notification settings - Fork 472
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
Revert upgrade to CoreDNS 1.5.0 #307
Conversation
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
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: MrHohn, prameshj 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 |
Hello, is any updates for this? |
We need atleast prometheus version 0.9.3, but the current skydns code has a constraint on version 0.8.0. I submitted skynetservices/skydns#350 for review, but have not gotten an update. I will modify this repo to use a fork of skydns and modify it there. |
Thank you. How about the bug around |
I haven't had a chance to debug that. Will do as part of my ongoing change. In the meantime, if you have any insights to share on the cleanup issue, that would be very helpful. |
I did some tries, instead of appending to the tail of |
The new image is not running the node-cache cleanup routine which deletes iptables rules and local interface created for node-cache. This is a problem when disabling the addon, if there is left over state.
Looks like the shutdown callbacks in forward plugin are taking longer/not completing before pod is shut down. The node-cache cleanup would be called after this.
Reverting the upgrade to get the image into k/k before code freeze.
Created an issue to rootcause this and upgrade to 1.5.0 - #306