liquidmetal-dev / liquidmetal-dev/cluster-api-provider-microvm
Update to CAPI v1beta2 Contract
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 157
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
We need to update the provider to the v1beta2 contract before v1beta1 is dropped.
Tasks:
- [ ] Adopt v1beta2 internally (and CAPI v1.11+) - CAPMVM types willl adhere to v1beta1 contract
- [ ] Do release
- [ ] Create v1alpha2 API version
- [ ] Add v1beta2 fields
- [ ] Mark old fields as deprecated
- [ ] Add metav1.Conditions
- [ ] Do release
Ref: https://cluster-api.sigs.k8s.io/developer/providers/migrations/v1.10-to-v1.11#suggested-changes-for-providers
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 with the linked Cluster API v1.10-to-v1.11 migration guide, then locate the provider's API types and release process. Work through the listed v1beta2 and v1alpha2 compatibility, deprecation, and Conditions tasks; done means the checklist is complete and the requested releases are made.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- infrastructure
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100