Skip to content

Umbrella issue: API changes / wish list #12570

@sbueringer

Description

@sbueringer

Goal of this issue is to provide an overview over issues related to API changes.

Let's try to make it explicitly clear going forward which changes require an apiVersion bump when we add new issues to the list

General

  • Consider to stop embedding structs, e.g.:
    • Machine struct directly in MD/MS (e.g. fields like clusterName, providerID don't belong there)
  • Improve CRD printcolumns

ClusterClass & Cluster.spec.topology:

Cluster:

Machine:

MachineDeployment

MachineHealthCheck

MachinePool:

Finalizers:

Backlog: (require some design/proposal)

Metadata

Metadata

Assignees

Labels

kind/api-changeCategorizes issue or PR as related to adding, removing, or otherwise changing an APIlifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.priority/backlogHigher priority than priority/awaiting-more-evidence.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