Configurable machine replacement #10946
Labels
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
kind/api-change
Categorizes issue or PR as related to adding, removing, or otherwise changing an API
kind/feature
Categorizes issue or PR as related to a new feature.
priority/important-longterm
Important over the long term, but may not be staffed and/or may need multiple releases to complete.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
What would you like to be added (User Story)?
As a operator i would like to be able to configure a time after machines are getting replaced automatically for testing and security reasons.
Detailed Description
Problem Statement:
Regularly replacing machines help in testing application behavior during rolling updates and ensures machines are refreshed periodically, especially important after security incidents.
Proposed Solution:
Implement
rolloutBefore.machineExpiry{Minutes,Hours,Days}
parameter within the Cluster API (likerolloutBefore.certificatesExpiryDays
implemented for KCP), allowing users to specify the maximum time a machine should exist before being automatically replaced.Benefits:
Impact:
Anything else you would like to add?
Current workarounds:
spec.rolloutAfter
periodically via CronJob for MachineDeploymentclusterctl alpha rollout restart machinedeployment/my-md-0
periodicallyLabel(s) to be applied
/kind feature
One or more /area label. See https://github.com/kubernetes-sigs/cluster-api/labels?q=area for the list of labels.
The text was updated successfully, but these errors were encountered: