isopod
isopod copied to clipboard
Garbage collection / pruning
Can isopod delete old resources that have been removed from the config?
Not yet as of today, but we will probably take a similar approach as that of helm 3 to a) create a tombstone configmap for each rollout, b) make this configmap the OwnerReference of all k8s objects created in this rollout, c) delete previous tombstone configmaps so dangling objects will be deleted cascadingly.
Step a) has been implemented but not the rest. One of the reasons that the garbage collection feature has been de-prioritized is that the correctness of the rollout is unaffected even without gc. It is still nice to have tho.
Is there a timeline on this sort of functionality? Would absolutely love to see it.