-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Configurable machine replacement #10946
Comments
/triage accepted |
q: is this about replacing nodes (the node at Kubernetes level) or the entire machine where the node is hosted? |
Hi @fabriziopandini it's about machines, i'll update the issue. |
ACK, thanks for the clarification |
@fabriziopandini: GuidelinesPlease ensure that the issue body includes answers to the following questions:
For more details on the requirements of such an issue, please see here and ensure that they are met. If this request no longer meets these requirements, the label can be removed In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
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: