Consider deprecation of revision management in MachineDeployments #10479
Labels
kind/api-change
Categorizes issue or PR as related to adding, removing, or otherwise changing an API
kind/cleanup
Categorizes issue or PR as related to cleaning up code, process, or technical debt.
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
priority/backlog
Higher priority than priority/awaiting-more-evidence.
As of today MachineDeployments manage a history of MachineSet objects.
This feature roughly consists of:
This feature (afaik) has been mostly copied from k/k Deployments & ReplicaSets
Reasons why we should consider deprecation:
So overall I think considering the current state of the feature, it's interoperability and that it's as far as we can tell not really used we should really consider if it's worth the complexity and otherwise consider deprecation.
If you are using the feature, please let us know.
The text was updated successfully, but these errors were encountered: