liquidmetal-dev / liquidmetal-dev/cluster-api-provider-microvm
Change API to use a separate Kind for load balancer
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 157
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
**Describe the solution you'd like:**
The cluster template currently sets the control plane endpoint before the api server load balancer is available, this causes errors in the CAPI controllers.
Change to a separate kind for a load balancer and only populate the contriol plane endpoint when its available.
**Why do you want this feature:**
**Anything else you would like to add:**
[Miscellaneous information that will assist in solving the issue.]
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the cluster template and the CAPI controller handling for the control plane endpoint and load balancer. Define how the separate load-balancer Kind becomes available, then ensure the endpoint is populated only afterward and verify that the CAPI controllers no longer receive an unavailable endpoint.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend-api-design, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100