You’ve got the etcd pod started, the apiserver pod should be started soon after. If you see it get stuck waiting for the kube-apiserver container to be created, I would take a look at the logs under /var/log/pods to see if there are any errors.

2023-04-17T20:54:26.138048682Z stderr F {"level":"info","ts":"2023-04-17T20:54:26.137Z","caller":"embed/etcd.go:308","msg":"starting an etcd server","etcd-version":"3.5.4","git-sha":"Not provided (use ./build instead of go build)","go-version":"go1.16.10b7","go-os":"linux","go-arch":"amd64","max-cpu-set":1,"max-cpu-available":1,"member-initialized":false,"name":"rke2-a4831e51","data-dir":"/var/lib/rancher/rke2/server/db/etcd","wal-dir":"","wal-dir-dedicated":"","member-dir":"/var/lib/rancher/rke2/server/db/etcd/member","force-new-cluster":false,"heartbeat-interval":"500ms","election-timeout":"5s","initial-election-tick-advance":true,"snapshot-count":10000,"snapshot-catchup-entries":5000,"initial-advertise-peer-urls":["https://192.168.1.89:2380"],"listen-peer-urls":["https://127.0.0.1:2380","https://192.168.1.89:2380"],"advertise-client-urls":["https://192.168.1.89:2379"],"listen-client-urls":["https://127.0.0.1:2379","https://192.168.1.89:2379"],"listen-metrics-urls":["http://127.0.0.1:2381"],"cors":["*"],"host-whitelist":["*"],"initial-cluster":"rke2-a4831e51=https://192.168.1.89:2380","initial-cluster-state":"new","initial-cluster-token":"etcd-cluster","quota-size-bytes":2147483648,"pre-vote":true,"initial-corrupt-check":true,"corrupt-check-time-interval":"0s","auto-compaction-mode":"","auto-compaction-retention":"0s","auto-compaction-interval":"0s","discovery-url":"","discovery-proxy":"","downgrade-check-interval":"5s"}

attach please (as above), don’t copy-paste

How much memory do you have on this node, like 1GB? It doesn’t have enough to run more than just the etcd pod.