Closed exolab closed 3 years ago
@exolab please try this PR (you will have to compile it): https://github.com/kubermatic/kubeone/pull/1380, this PR will be release as kubeone v1.2.3.
@kron4eg Thank you for the swift reply and PR. We did build kubeone ourselves and have since migrated to the released v1.2.3. However, we still see the same thing happening.
nslookup google.com
just fine, we get fast responsesnslookup
again and get no response ;; connection timed out; no servers could be reached
[ERROR] plugin/errors: 2 route53.amazonaws.com.cluster.local. A: dial tcp 10.106.52.115:53: i/o timeout
This only happens after the second kubeone run.
We run kubeone a second time. All the canal pods get terminated and restarted.
are you using kubeone apply each time, or kubeone install?
I can't reproduce this issue. Can you please share the deployment used to spawn the pods.
We run kubeone a second time. All the canal pods get terminated and restarted.
are you using kubeone apply each time, or kubeone install?
We are using apply in both cases...
I can't reproduce this issue. Can you please share the deployment used to spawn the pods.
I am not entirely sure what you mean. This is how we are spawning the pod on the worker node:
kubectl run -i --tty dnsutils --image gcr.io/kubernetes-e2e-test-images/dnsutils:1.3 --kubeconfig terraform/credentials/kubeconfig --restart=Never -- sh
@kron4eg I can confirm that after deploying a fresh cluster using the most recent patched version and then running kubeone apply
a second time no longer leads to the problem I had.
Thank you so much for your impressively swift reaction and resolution, @kron4eg!
I am using kubeone to set up a cluster on Hetzner cloud. After the initial run, things mostly work. There is a problem reaching kube-dns-upstream from pods on the worker nodes, but that can be fixed by doing a rolling restart of coredns.
However, after I run kubeone for a second time, canal gets redeployed, which then renders the cluster unusable. Every request seems to be taking 10 seconds (which of course makes debugging a pain).
This is how I execute kubeone (on both runs).
kubeone.yaml
andtf.json
are identical on both runs. I am using kubeone 1.2.2 (and have also tried 1.2.1) and have tried with kubernetes 1.20 as well.Does anyone have an idea what might be causing this? What logs should I look at specifically for debugging?