Skip to content

Complete CAPD => CAPDev transition #13270

@sbueringer

Description

@sbueringer

A while ago we started the transition from CAPD to CAPDev, which was outlined in this proposal: https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/proposals/20250124-From%20CAPD(docker)%20to%20CAPD(dev)%20.md

Completed:

Open tasks:

  • DevMachinePool with docker backend
  • Clearly deprecate DockerMachine / DockerCluster / DockerMachinePool CRDs (they were already deprecated, we just didn't deprecate the CRDs & Go types afaik)
  • Migrate all E2E tests to DevCluster, DevMachine and DevMachinePool (with Docker backend) (includes e2e tests & YAMLs + probably test extension)
    • All e2e tests except clusterctl upgrade (should be straightforward)
    • clusterctl upgrade (let's discuss once we get here, we either have to backport DevMachinePool or drop MachinePool from these tests)
  • Consider migrating some E2E tests from the docker to the in-memory backend to speed up e2e tests (TBD with maintainers which)

At a later stage: (timing TBD)

  • Remove DockerCluster, DockerMachine and DockerMachinePool

Metadata

Metadata

Assignees

Labels

area/provider/infrastructure-dockerIssues or PRs related to the docker infrastructure providerkind/featureCategorizes issue or PR as related to a new feature.priority/important-longtermImportant over the long term, but may not be staffed and/or may need multiple releases to complete.triage/acceptedIndicates an issue or PR is ready to be actively worked on.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions