PanKaker

Okay. So, from logs of kubectl I can see that for some reasons: 1) Kubectl trying to make a request https://10.101.3.50:6443/apis/projectcalico.org/v3?timeout=32s 2) After 5 sec we are reaching deadline (Service...

Hi! Do you have any update?

Hi! Yes, API server is in a container. I didn't setup server manually. It was part of kubeadm init task.

By 'Restart kube-apiserver container' I meant this command: docker ps | grep "k8s_kube-apiserver" | docker kill $(awk '{print $1}')

Kubernetes were installed with pod network 10.233.64.0/18. Maybe it will be useful. This is my custom-resources file: ``` apiVersion: operator.tigera.io/v1 kind: Installation metadata: name: default spec: # Configures Calico networking....

UPD: I was able to reproduce the same issue for 2 clusters ( 2 nodes setup - 1 cp and 1 worker node)

Tested with 2 node cluster. Each host has 2 NICs (1 ssh interface, 1 node interface 10.101.3.0/24) 1) Create a kubeadm cluster with config kubeadm init --config ./config-init.yaml ``` apiVersion:...

I can try to reproduce the issue and send more logs from kubernetes/calico/etcd

Hi, @srebhan, @powersj! Is it possible to add me to Co-authored list of the PR/commit to master? https://github.com/influxdata/telegraf/pull/12452/commits/1a931cd9747f09649495aa435f5b67ec4d38b1f7 I was a person who implemented this feature, but because of lack...