Closed P4sca1 closed 1 month ago
Well. This is not possible.
We run helm operations even before the machine-controller, to allow deploying of CNI (like you do), to have some Ready nodes.
In your case I recommend you to set tolerations (see https://github.com/cilium/cilium/blob/v1.15.6/install/kubernetes/cilium/values.yaml#L994) to open control-plane nodes for certgen Job.
What happened?
The kubeone deployment gets stuck, as it is waiting for jobs to finish. The jobs can't finish, because no worker nodes exist. I am using dynamicWorkers only.
Expected behavior
I would expect kubeone to create the
MachineDeployment
right after themachine-controller
is deployed, so that worker nodes start to spawn and helm deployments can successfully finish.How to reproduce the issue?
The issue occurs during initial deployment and can be fixed by manually creating the MachineDeployment.
What KubeOne version are you using?
Provide your KubeOneCluster manifest here (if applicable)
What cloud provider are you running on?
Hetzner Cloud
What operating system are you running in your cluster?
Flatcar Linux Beta for Control Plane Ubuntu 22 for Worker Nodes
Additional information
Cilium helm values: