I0220 13:52:02.661015 1 shared_informer.go:240] Waiting for caches to sync for service config W0220 13:52:02.614777 1 sysinfo.go:203] Nodes topology is not available, providing CPU topology I0220 13:52:02.605151 1 server_others.go:491] "Detect-local-mode set to ClusterCIDR, but no IPv6 cluster CIDR defined,, defaulting to no-op detect-local for IPv6" $ kubectl logs kube-proxy-gkkxq -n kube-system $ kubectl get pods -n kube-system -o=wide NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE SELECTORĮcho-server ClusterIP 10.11.213.180 8080/TCP 24h app=echo-server $ kubectl get services -n kube-verify -o=wide I suspect my kube-proxy is not working as it should. Why? Requests simply time out, while requests to the pod's cluster IP work fine. However, I cannot reach the service's cluster IP from any of the nodes. I then created my own kube-verify namespace, put a deployment of the echo-server into it, and created a service for it. The gist of it is that the control plane was created using this command kubeadm init -token= -kubernetes-version=v1.23.3 -pod-network-cidr=10.1.0.0/16 -service-cidr=10.11.0.0/16 -control-plane-endpoint=10.0.4.16 -node-name=rpi-1-1 I installed a k8s 1.23.3 cluster on four raspberry pi's running raspberrypi OS 11 (bullseye) arm64 mostly by following this guide.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |