Max Gautier

Not to my knowledge, that's just a bit unusual^.

> I can confirm the bug on a cluster with 3 control planes and 3 worker nodes, also deployed with dns_mode: coredns. I can also confirm the "workaround" deleting the...

For instance I just tried running upgrade cluster on a fresh cluster while running the following on the first master: (the jq test that we get the correct ports on...

I'll try with that, see if I can finally get a reproducer, thanks :+1:

So the transition (that's not completely complete) goes something like this: ```json [ [ { "name": "dns", "port": 53, "protocol": "UDP", "targetPort": 53 }, { "name": "dns-tcp", "port": 53, "protocol":...

Apparently, this also happens when using `--tags coredns` (so kubeadm is out IMO). I think this has something to do with the way kubectl do it's apply.

We're probably hitting something like this : https://github.com/kubernetes/kubernetes/issues/39188#issuecomment-269550385 Another potentialy relevant : https://ben-lab.github.io/kubernetes-UDP-TCP-bug-same-port/ TL;DR : kubectl apply does the wrong thing because it does not use the correct key to...

Using server-side apply **does** fix the issue. I'm working on a PR (mentioned above) but it needs to refactor some stuff in boostrap-os and kubernetes/preinstall.

/retitle coredns UDP service port point to TCP pod port when upgrading from 23.* This affects master as well (AFAICT). @yankay or @floryut : can you pin the issue until...

Using `kubectl apply -f --server-side=true` (check the flag name, I'm writing this from memory) should also work ; it's what the fix I'm working on essentially is.