-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Open
Labels
kind/api-changeCategorizes issue or PR as related to adding, removing, or otherwise changing an APICategorizes 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.Indicates that an issue or PR should not be auto-closed due to staleness.priority/backlogHigher priority than priority/awaiting-more-evidence.Higher priority than priority/awaiting-more-evidence.triage/acceptedIndicates an issue or PR is ready to be actively worked on.Indicates an issue or PR is ready to be actively worked on.
Description
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
- Consider how we can improve our columns once we can rely on CEL for CRD columns:
- Consider introducing a class.namespace column on the Cluster object once we can rely on CEL support for CRD columns: 🌱 Provide namespace of the referenced ClusterClass in
TEMPLATENAMESPACE
#11802 (comment) - Improve Machine InternalIP/ExternalIP columns to show all IPs
- Consider introducing a class.namespace column on the Cluster object once we can rely on CEL support for CRD columns: 🌱 Provide namespace of the referenced ClusterClass in
- Consider how we can improve our columns once we can rely on CEL for CRD columns:
ClusterClass & Cluster.spec.topology:
- Enable lifecycle hooks explicitly in the ClusterClass #8211
- Provide explicit definition of variables scope in ClusterClass #6706
Cluster:
Machine:
- [TBD] Take another look at Bootstrap
- Check in all the places where we use MachineSpec (MD/MS/MP/...)
- Think about use cases where user set dataSecretName: "" (usually because they don't want to use bootstrap) (BootstrapConfig should be optional for MachinePool based ClusterClass #10943 (comment))
- [TBD] Allow user to opt-in to Node draining during Cluster delete #9692
MachineDeployment
- cleanup revisionHistoryAnnotation after ⚠️ Drop revisionHistory in MachineDeployment #12274
- [TBD] Paused behaviour is inconsistent #6966:
- Check behavior of upstream Deployment.spec.paused, see if the same makes sense for us, if yes => suggest to rename the field to disambiguate
MachineHealthCheck
- Improve UX of MachineHealthCheckStatus fields #5291 [not planned]
MachinePool:
- MachinePools cannot be upgraded atomically when used with managed providers #7248 [not planned] [TBD if blocker for MP graduation]
Finalizers:
Backlog: (require some design/proposal)
mcbenjemaa
Metadata
Metadata
Assignees
Labels
kind/api-changeCategorizes issue or PR as related to adding, removing, or otherwise changing an APICategorizes 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.Indicates that an issue or PR should not be auto-closed due to staleness.priority/backlogHigher priority than priority/awaiting-more-evidence.Higher priority than priority/awaiting-more-evidence.triage/acceptedIndicates an issue or PR is ready to be actively worked on.Indicates an issue or PR is ready to be actively worked on.