Hi Team I’m using k3s and cilium clustermesh using...
# general
s
Hi Team I’m using k3s and cilium clustermesh using nodeport service type, I think it’s how k3s uses kubelet
ilium clustermesh status ⚠️ Service type NodePort detected! Service may fail when nodes are removed from the cluster! Service "clustermesh-apiserver" of type "NodePort" found Cluster access information is available: ◦ 159.x.x.x:32394 Deployment clustermesh-apiserver is ready ℹ️ KVStoreMesh is enabled Error: Unable to determine status: unable to determine status of pod "cilium-n7xbq": command failed (pod=kube-system/cilium-n7xbq, container=cilium-agent): Internal error occurred: error sending request: Post "https://142.x.x.x:10250/exec/kube-system/cilium-n7xbq/cilium-agent?command=cilium&command=status&command=-o&command=json&error=1&output=1": proxy error from 127.0.0.1:6443 while dialing 142.x.x.x:10250, code 502: 502 Bad Gateway