Michael Müller:
kube-proxy binds to ipv6 only.
Hi. I have setup a v1.15 cluster with kubadm
I ran a nginx pod and then created a service of type nodePort, I only see a port binding of the 3xxxx port on v6 address, but not on v4 ip address of the nodes, checking by netstat
Accessing the nginx by curl does not work , because nodename is resolved to ipv4…
I expected , that kube-proxy would bind to node ipv4 address. Where am I going wrong ?
And dualstack seems to be supported from version 1.20 on …
Thanks for help and clarification, as I really get puzzled…
Michael Müller:
Thanks a lot.
But , well let me be more precise of what my question is.
I did a simple installation with kubeadm
Without specifying an cidr’s .
Master was just initialized with " kubeadm init"
Joined the nodes and deployed weave cni
Due to other reasons I used and need to use k8s version 1.15.
My expectation is that a nodePort service wold bind to the ipv4 address on each node by kube-proxy.
So I would be able to access my service on every node.
Is this correct?
Obviously the bind is only done on ipv6 addresses.
And this is what I don’t understand.
Dual stack might be a solution, but as far as I’m aware, this is not supported by k8s version 1.15.
So this seems to be no option. Right?
Thanks a lot.
unnivkn:
check all the highlighted texts, to make sure only IPv4 configured
unnivkn:
refer this kubeadm init dual stack doc. You may remove IPv6 & have a try