Rancherd and bind-address

Rancher 2.x
1

Hi,

can it be the --bind-address argument in configuration for rancherd or rke2 is ignored for some reason?

I have this in /etc/rancher/rke2/config.yaml

write-kubeconfig-mode: "0644"
token: "..."
tls-san:
 - ...
bind-address: 10.0.0.11
node-ip: 10.0.0.11
kube-apiserver-arg:
  - kubelet-preferred-address-types=InternalIP,Hostname,ExternalIP
  - bind-address=10.0.0.11
...

but kube-apiserver appears with --bind-address 0.0.0.0

image
image1197×72 4.75 KB

Any idea, what’s wrong here?

Rancherd: v2.5.8
Kubernetes: v1.20.5+rke2r1

Kind regards,
Michael

1 Like