[Release-1.27] - Disable http/grpc mux for etcd

[brandond]

Backport fix for Disable http/grpc mux for etcd

• Disable http/grpc mux for etcd #8415

[mdrahman-suse]

Validated on release-1.27 branch with commit bd04941

Environment Details

Infrastructure

• Cloud
• Hosted

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

Ubuntu 22.04.2 LTS (GNU/Linux 5.15.0-1031-aws x86_64)

Cluster Configuration:

1 server

Config.yaml:

write-kubeconfig-mode: 644
cluster-init: true
node-external-ip: <public-ip>

Testing Steps

1. Copy config.yaml

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

2. Install k3s
3. Wait for the cluster to be up and running
4. Check the logs using: $ sudo journalctl -u k3s | grep "Running http"
5. Ensure no error message is displayed

Replication Results:

• k3s version used for replication:

$ k3s -v
k3s version v1.27.6+k3s1 (bd04941a)
go version go1.20.8

• Observed warn message in logs

$ sudo journalctl -u k3s | grep "Running http"
Oct 16 18:20:26 ip-xxx-xx-xx-230 k3s[1728]: {"level":"warn","ts":"2023-10-16T18:20:26.042449Z","caller":"embed/config.go:673","msg":"Running http and grpc server on single port. This is not recommended for production."}
Oct 16 18:20:26 ip-xxx-xx-xx-230 k3s[1728]: {"level":"warn","ts":"2023-10-16T18:20:26.042761Z","caller":"embed/config.go:673","msg":"Running http and grpc server on single port. This is not recommended for production."}

Validation Results:

• k3s version used for validation:

$ k3s -v
k3s version v1.27.6+k3s-78e57bc9 (78e57bc9)
go version go1.20.8

• Observed NO warn message in logs

$ sudo journalctl -u k3s | grep "Running http"
ubuntu@ip-xxx-xx-xx-230:~$