cluster-etcd secret is not created during cloud-init setup #403
Labels
kind/bug
Something isn't working
needs-priority
Indicates an issue or PR needs a priority assigning to it
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
What happened:
relevant excerpt fron cloud-init userdata generated by provider:
- 'kubectl create secret tls cluster-etcd -o yaml --dry-run=client -n kube-system --cert=/var/lib/rancher/rke2/server/tls/etcd/server-ca.crt --key=/var/lib/rancher/rke2/server/tls/etcd/server-ca.key --kubeconfig /etc/rancher/rke2/rke2.yaml | kubectl apply -f- --kubeconfig /etc/rancher/rke2/rke2.yaml'
as a result, we constantly get the following info log message
Cluster does not provide etcd certificates for creating child etcd ctrlclient.Please scale up the CP nodes by one to bootstrap the etcd secret content." controller="rke2controlplane" controllerGroup="controlplane.cluster.x-k8s.io" controllerKind="RKE2ControlPlane" [...]
What did you expect to happen:
Full path to rke2 kubectl binary be used /var/lib/rancher/rke2/bin/kubectl or $PATH being modified properly before the invocation
How to reproduce it:
Setup a new cluster
Environment:
The text was updated successfully, but these errors were encountered: