liquidmetal-dev/cluster-api-provider-microvm

Update to CAPI v1beta2 Contract

Open

#354 opened on May 5, 2026

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Go (21 forks)auto 404
area/apiarea/dependencyhelp wantedkind/dependencieskind/refactor

Repository metrics

Stars
 (154 stars)
PR merge metrics
 (PR metrics pending)

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

Research direction
Review the CAPI v1beta2 contract migration guide and identify all necessary changes to the provider's types, controllers, and webhooks. Focus on adopting v1beta2 internally first, then follow the checklist for API versioning and deprecation.
Tech stack
go
Domain
backendinfrastructureapi
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GoKubernetesCluster API
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20