Update objects accumulate indefinitely in the system, and the operator should cleanup the old completed updates, e.g. after a week or so.
Should the Update controller handle the cleanup uniformly? Or should the Stack controller handle the cleanup for the updates that it owns? I would lean towards the former, by introducing a Update.spec.ttlSecondsAfterFinished field that the Stack controller may set and is implemented by the Update controller.
Update
objects accumulate indefinitely in the system, and the operator should cleanup the old completed updates, e.g. after a week or so.Should the Update controller handle the cleanup uniformly? Or should the Stack controller handle the cleanup for the updates that it owns? I would lean towards the former, by introducing a
Update.spec.ttlSecondsAfterFinished
field that theStack
controller may set and is implemented by the Update controller.See https://kubernetes.io/docs/concepts/workloads/controllers/ttlafterfinished/