Debug - Broken ETCD cluster
Issue A few days ago I was doing an upgrade over a Kubernetes control plane in ClusterAPI which only had one node (this client didn’t have enough hardware for HA at the moment). I was using Mikroways latest vSphere CAPI Helm Chart and I accidentaly added a wrong value in the KubeApiServer extra args section. Specifically in this value: .kubeadm.clusterConfiguration.apiServer.extraArgs The thing was that after applying the changes, a new node was created but it didn’t register correctly. KubeApiServer couldn’t be added to the cluster because of the incorrect values in its arguments and was stuck in this state. ...