The nodeport defined by the k8s cluster cannot take effect. There is no corresponding port listening in netstat
Check the Kube proxy log and find that
Guess, the address has run out. Temporary solution:
Modify Kube proxy configuration
kubectl edit cm kube-proxy -n kube-system
# Add in the Path of nodePortAddresses
nodePortAddresses: ["172.16.0.0/16"]
# Delete kube-proxy pod working
The cluster is generated using kubedm. I guess you need to specify the address range of nodeportaddresses in kubedm
Similar Posts:
- kube-proxy Error: Failed to delete stale service IP [How to Solve]
- K8S error: Unable to connect to the server: x509: certificate signed by unknown authority [Solved]
- K8s binary deployment start API-server error: Error: unknown flag: –etcdservers
- [Solved] K8s cannot delete the namespace. It is always in the terminating state.
- Other Master Nodes Add to the Cluster After Reset Error: CONTEXT DEADLINE EXCEEDED
- [Solved] Error: failed to install CRD crds/crd-alertmanager.yaml: unable to recognize “”: no matches for kind “CustomResourceDefinition” in version “apiextensions.k8s.io/v1beta1”
- K8S Error: no metrics known for node [How to Solve]
- K8s version 1.20x nfs dynamic storage error: persistentvolume-controller waiting for a volume to be created, either by external provisioner “qgg-nfs-storage” or manually created by system administrator
- Proxy error: Could not proxy request [How to Solve]
- [Solved] kubeadm join 192.168.50.66:6443 –token 0109we.c3a3ofn0y0lmp0w9 –discovery-token-ca-cert-hash sha256:262f5eefdbeba51e6875cba5ed6e34061ad679f8a21f6e295d9fbd5ef05757e4