cluster-api-provider-tencent
cluster-api-provider-tencent copied to clipboard
LeaderElectionID should be unique
This issue was reported in other providers - Running several Cluster API pods (e.g. CAPI + CABPK + an infra provider) in the same namespace results in leader election errors. Additional details here - kubernetes-sigs/cluster-api-bootstrap-provider-kubeadm#271