-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
figure out why create is broken after https://github.com/kubernetes/kubernetes/pull/68890 #43
Comments
As far as I can tell this change means if there is a cluster DNS configured on the kubelet, critical static system pods will now use it.
Not sure how this is supposed to work correctly... |
Specifically the api server talks to itself via |
update:
works fine. moving one commit forward to:
breaks This seems to confirm that it's related to the DNS policy change. |
found it here: kubernetes/kubernetes#69195 work around is here: #45 |
well we know why, and have a work around. upstreaming improvements now... |
[EOS-10849] Integrar GCP en cloud-provisioner (Part II): Add gcp support to keos.yaml
/priority critical-urgent
/assign
I've pinned down CI failures to after kubernetes/kubernetes#68890 merged and I can replicate this locally, but I'm not sure why this broke
kind
just yet. This reliably breaks cluster up.This changed how some of the static pods are handling DNS, before this they would have used host DNS instead of cluster DNS. I'm not actually sure how this is supposed to bootstrap properly.
FYI @spiffxp :(
cc @MrHohn who I suspect is familiar with DNS policy 😉 and may be able to lend a hand
The text was updated successfully, but these errors were encountered: