Hello, This is my kubelet config on Node 1 for example.
/etc/systemd/system/kubelet.service I configured kubelet like this ExecStart=/usr/local/bin/kubelet --allow-privileged --v=2 --cloud-provider="" --register-node=true --fail-swap-on=false --require-kubeconfig --pod-manifest-path="/etc/kubernetes/manifests" --network-plugin=kubenet --non-masquerade-cidr=10.20.0.0/16 --pod-cidr=10.20.0.0/24 --node-ip=10.20.0.1 [Install] WantedBy=multi-user.target And bridge(cbr0) ip on Node1-4 Node 1 cbr0 10.20.0.1 Node 2 cbr0 10.20.1.1 Node 3 cbr0 10.20.2.1 Node 4 cbr0 10.20.3.1 If I deploy a pod on Node2-4, the container in the pod fails to start with this error (it has a connection issue to 10.20.0.1 on node 1). > Error while initializing connection to Kubernetes apiserver. This most likely means that the cluster is misconfigured (e.g., it has invalid apiserver certificates or service accounts configuration) or the --apiserver-host param points to a server that does not exist. Reason: Get http://10.20.0.1:8080/version: dial tcp 10.20.0.1:8080: i/o timeout If I deploy a pod on Node 1, the container in the pod runs successfully (I guess it's for local networking). I suspect it's a routing issue from pod on Node2-4 to Node1 (10.20.0.1). Does anyone have a recommendation where I should fix to resolve the problem? Thanks, Jerry -- You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and Q&A" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/kubernetes-users. For more options, visit https://groups.google.com/d/optout.
