baidu / baidu/cluster-api-provider-baiducloud
LeaderElectionID should be unique
Open
- Dominant language
- Go
- Stars
- 14
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
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. More details here - kubernetes-sigs/cluster-api-bootstrap-provider-kubeadm#271
Contributor guide
Research direction
Start by reading the linked cluster-api-bootstrap-provider-kubeadm#271 report and locating this provider's leader-election configuration. Confirm how several Cluster API provider pods in one namespace are assigned election IDs; done means they no longer conflict when deployed together.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100