A way to tell if a custer that is just boostraped is ready for CNI installation

[myMarck]

There should be a way from a script to know if a cluster ready for installation of an CNI if kube-proxy is disabled

In the seconds after "talosctl bootstrap" the cluster is not ready for installation of a 3 party CNI because etcd and other services are not up and running.

But currently its not possible from a script to know if the cluster is ready because "talosctl health" is stuck returning

talosctl -n 192.168.1.30 health --wait-timeout 10s
discovered nodes: ["192.168.1.30" "192.168.1.33" "192.168.1.34" "192.168.1.35"]
waiting for etcd to be healthy: ...
waiting for etcd to be healthy: OK
waiting for etcd members to be consistent across nodes: ...
waiting for etcd members to be consistent across nodes: OK
waiting for etcd members to be control plane nodes: ...
waiting for etcd members to be control plane nodes: OK
waiting for apid to be ready: ...
waiting for apid to be ready: OK
waiting for all nodes memory sizes: ...
waiting for all nodes memory sizes: OK
waiting for all nodes disk sizes: ...
waiting for all nodes disk sizes: OK
waiting for no diagnostics: ...
waiting for no diagnostics: active diagnostics: 192.168.1.30: kubelet server certificate rotation is enabled, but CSR is not approved; 192.168.1.33: kubelet server certificate rotation is enabled, but CSR is not approved; 192.168.1.34: kubelet server certificate rotation is enabled, but CSR is not approved; 192.168.1.35: kubelet server certificate rotation is enabled, but CSR is not approved

[smira]

You can use kubectl apply before it succeeds, or anything idempotent like that.

In your case, server-side kubelet certificate issue is enabled, but no CSR approver is installed, which is unrelated.

[myMarck]

Hello Smira
You are right - If i remove the code to enable metrics sever it works.