sparse-magazine-9503
11/10/2025, 3:25 AMprofile: cis parameter on the config.yaml, creating etcd user, and setting up kernel parameters.
When I try to do the same thing on Rocky Linux, it is not working. SELinux and firewalld are disabled.
kube-apiserver container logs
BalancerAttributes: {"<%!p(pickfirstleaf.managedByPickfirstKeyType={})>": "<%!p(bool=true)>" }}. Err: connection error: desc = "transport: Error while dialing: dial tcp 127.0.0.1:2379: operation was canceled"
journalctl logs for rke2
Nov 08 09:58:23 master1.rockystartlocal rke2[4731]: time="2025-11-08T09:58:23-05:00" level=warning msg="Failed to list nodes with etcd role: runtime core not ready"
Nov 08 09:58:30 master1.rockystartlocal rke2[4731]: time="2025-11-08T09:58:30-05:00" level=info msg="Pod for etcd is synced"
Nov 08 09:58:30 master1.rockystartlocal rke2[4731]: time="2025-11-08T09:58:30-05:00" level=info msg="Pod for kube-apiserver not synced (pod sandbox has changed), retrying"
Upon checking the containers with crictl, etcd container is running and api-server has exited. When I used etcdctl to check the health of etcd, it was healthy.sparse-magazine-9503
11/10/2025, 3:26 AMcreamy-pencil-82913
11/10/2025, 3:46 AM