Garbage collection for Update objects #733
Labels
good-first-issue
Start here if you'd like to start contributing to Pulumi
impact/usability
Something that impacts users' ability to use the product easily and intuitively
kind/enhancement
Improvements or new features
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/
The text was updated successfully, but these errors were encountered: