[release-1.25] Tunnel authorizer sets port before Kubelet is ready

[brandond]

• Backport Tunnel authorizer sets port before Kubelet is ready #7047

[mdrahman-suse]

Validated on version v1.25.8-rc2+k3s1

Environment Details

Infrastructure

• Cloud
• Hosted

Node(s) CPU architecture, OS, and Version:

Linux 5.15.0-1026-aws #30-Ubuntu SMP Wed Nov 23 14:15:21 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
PRETTY_NAME="Ubuntu 22.04.1 LTS"

Cluster Configuration:

1 server

Config.yaml:

write-kubeconfig-mode: 644
cluster-init: true

Testing Steps

1. Copy config.yaml

$ sudo mkdir -p /etc/rancher/k3s && sudo cp config.yaml /etc/rancher/k3s

2. Install k3s
3. Ensure cluster is up
4. Check log for default port 10250
5. Update /etc/rancher/k3s/config.yaml by adding below

kubelet-arg:
  - port=11250

6. Restart k3s
7. Check log for updated port

Replication Results:

• k3s version used for replication:

k3s version v1.25.7+k3s1 (f7c20e23)
go version go1.19.6

• Default port before restart

$ sudo journalctl -u k3s | grep -i Tunnel
...
Mar 23 17:05:22 ip-172-31-34-37 k3s[1628]: time="2023-03-23T17:05:22Z" level=info msg="Tunnel authorizer set Kubelet Port 10250"

• Kubelet Port was not updated after restart

$ sudo journalctl -u k3s | grep -i Tunnel
...
Mar 23 17:09:04 ip-172-31-34-37 k3s[4103]: time="2023-03-23T17:09:04Z" level=info msg="Tunnel authorizer set Kubelet Port 10250"

Validation Results:

• k3s version used for validation:

k3s version v1.25.8-rc2+k3s1 (6c5ac022)
go version go1.19.7

• Default port before restart

$  sudo journalctl -u k3s | grep -i Tunnel
...
Mar 23 17:38:29 ip-172-31-34-37 k3s[5930]: time="2023-03-23T17:38:29Z" level=info msg="Tunnel authorizer set Kubelet Port 10250"

• Kubelet Port is updated after restart

$  sudo journalctl -u k3s | grep -i Tunnel
...
Mar 23 17:42:04 ip-172-31-34-37 k3s[8366]: time="2023-03-23T17:42:04Z" level=info msg="Tunnel authorizer set Kubelet Port 11250"