Is there any trick to adding a new RKE2 cluster on...
# rke2
s
Is there any trick to adding a new RKE2 cluster on digitalocean or ubuntu24? I think I have the same issue as this fella https://github.com/rancher/rancher/issues/50224
c
log in to the node and check the rancher-system-agent and rke2 logs in journald
that is just a generic message that indicates that something isn’t coming up and phoning home, if it was then you’d get more detailed status or errors
s
There's a few pages of logs with
/var/lib/rancher/rke2/bin/kubectl --kubeconfig /etc/rancher/rke2/rke2.yaml logs -n cattle-system cattle-cluster-agent-b65c555f7-svn78
A snippet of the only error I can find:
Copy code
time="2025-09-04T21:13:28Z" level=info msg="Rancher agent version v2.12.1 is starting"
time="2025-09-04T21:13:28Z" level=info msg="EnsureSecretForServiceAccount: waiting for secret [cattle-system:cattle-token-4jfkr] for service account [cattle-system:cattle] to be populated with token"
time="2025-09-04T21:13:28Z" level=info msg="EnsureSecretForServiceAccount: got the service account token for service account [cattle-system:cattle] in 6.904297ms"
time="2025-09-04T21:13:28Z" level=error msg="unable to read CA file from /etc/kubernetes/ssl/certs/serverca: open /etc/kubernetes/ssl/certs/serverca: no such file or directory"
time="2025-09-04T21:13:28Z" level=info msg="Connecting to <wss://rancher3.mycompany.com/v3/connect/register> with token starting with v5nzrg6bmrx567fnjjgrmrdq275"
time="2025-09-04T21:13:28Z" level=info msg="Connecting to proxy" url="<wss://rancher3.mycompany.com/v3/connect/register>"
time="2025-09-04T21:13:28Z" level=info msg="Starting /v1, Kind=Service controller"
time="2025-09-04T21:13:28Z" level=info msg="Running in single server mode, will not peer connections"
time="2025-09-04T21:13:28Z" level=info msg="Scanning NodeTemplates in namespace: cattle-global-nt, group: <http://nodetemplates.management.cattle.io|nodetemplates.management.cattle.io>"
Ahhh, think I found something
Copy code
Events:
  Type     Reason            Age                 From               Message
  ----     ------            ----                ----               -------
  Warning  FailedScheduling  29m (x11 over 79m)  default-scheduler  0/1 nodes are available: 1 node(s) had untolerated taint {<http://node-role.kubernetes.io/control-plane|node-role.kubernetes.io/control-plane>: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.
c
… did you not give it enough resources?
or did you add taints?