[Release-1.27] - k3s server process shows up as k3s agent in process list

[brandond]

Backport fix for k3s server process shows up as k3s agent in process list

• k3s server process shows up as k3s agent in process list #10616

[endawkins]

Validated on branch release-1.27 with commit 8c79522 / version 1.27

Environment Details

Infrastructure

• Cloud
• Hosted

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

Linux ip-172-31-2-17 5.15.0-1019-aws #23-Ubuntu SMP Wed Aug 17 18:33:13 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
PRETTY_NAME="Ubuntu 22.04.1 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.1 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy

Cluster Configuration:

N/A [Single node or HA is fine or a single server]

Config.yaml:

write-kubeconfig-mode: "0644"
tls-san:
  - fake.fqdn.value
node-name: [REDACTED]
protect-kernel-defaults: true
selinux: true
node-external-ip: [REDACTED]
node-ip: [REDACTED]
cluster-init: true
secrets-encryption: true
kube-apiserver-arg:
  - 'audit-log-path=/var/lib/rancher/k3s/server/logs/audit.log'
  - 'audit-policy-file=/var/lib/rancher/k3s/server/audit.yaml'
  - 'audit-log-maxage=30'
  - 'audit-log-maxbackup=10'
  - 'audit-log-maxsize=100'
  - 'request-timeout=300s'
  - 'service-account-lookup=true'
  - 'enable-admission-plugins=NodeRestriction,PodSecurity,NamespaceLifecycle,ServiceAccount'
  - 'admission-control-config-file=/var/lib/rancher/k3s/server/cluster-level-pss.yaml'
kube-controller-manager-arg:
  - 'terminated-pod-gc-threshold=10'
  - 'use-service-account-credentials=true'
kubelet-arg:
  - 'streaming-connection-idle-timeout=5m'

Additional files

N/A

Testing Steps

1. Copy config.yaml

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

2. Install k3s
3. kubectl get nodes,pods -A -o wide
4. ps auxfww | grep bin/k3s

Replication Results:

Replication here: #10621

Validation Results:

• k3s version used for validation:

k3s -v
k3s version v1.27.16+k3s-8c79522e (8c79522e)
go version go1.22.5

kubectl get nodes,pods -A -o wide
NAME                                              STATUS   ROLES                       AGE   VERSION                 INTERNAL-IP    EXTERNAL-IP     OS-IMAGE             KERNEL-VERSION    CONTAINER-RUNTIME
node/ip-172-31-2-17.us-east-2.compute.internal    Ready    control-plane,etcd,master   13m   v1.27.16+k3s-8c79522e   172.31.2.17    [REDACTED]      Ubuntu 22.04.1 LTS   5.15.0-1019-aws   containerd://1.7.20-k3s1.28
node/ip-172-31-3-141.us-east-2.compute.internal   Ready    <none>                      10m   v1.27.16+k3s-8c79522e   172.31.3.141   [REDACTED]      Ubuntu 22.04.1 LTS   5.15.0-1019-aws   containerd://1.7.20-k3s1.28

ps auxfww | grep bin/k3s
ubuntu     11028  0.0  0.0   7004  2168 pts/0    S+   03:38   0:00              \_ grep --color=auto bin/k3s
root        78

Additional context / logs:

N/A