Skip to content

Tracking issue for v1Beta2 #11947

@fabriziopandini

Description

@fabriziopandini

Introduce the new API type

P0: mandatory for first alpha
P1: nice 2 have for first alpha

Introduce support for compatible contracts

Improving status Implementation Phase2 (1.11)

Others

Open issues we should look into before the release

Testing

  • Check conditions in e2e tests: 🌱 add checker to validate conditions for v1beta2 #12111
  • Consider extending test/extension to produce a patch for extraArgs (v1beta1+v1beta2) for additional coverage
  • [P0] Fix unit / e2e test flakes, e.g.
  • Audit e2e test artifact YAMLs: we only expect fields that we set + fields that are defaulted
  • Consider to step up test coverage where API version is relevant (e.g. CC, topology controller, Runtime Extension)
  • [P1] Look at our logs and see if we can reduce the amount of logged errors
    • Combine with going through a few basic scenarios with watch on clusterctl describe (clusterctl upgrade / rollout / ... e.g. by running e2e test cases)
    • Filter out "well-known" API warnings in controllers (deprecated API is still used)
      • Consider hiding: " is deprecated; use controlplane.cluster.x-k8s.io/v1beta2 KubeadmControlPlaneTemplate"
    • The following errors don't need the entire stack trace:
      • "error creating watch machine-watchNodes for *v1.Node: connection down" (+ connection down error in general)
      • check for other cases

Metadata

Metadata

Labels

kind/featureCategorizes issue or PR as related to a new feature.priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.triage/acceptedIndicates an issue or PR is ready to be actively worked on.

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions