Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Garbage collection / pruning #19

Open
leoluk opened this issue Jan 2, 2020 · 2 comments
Open

Garbage collection / pruning #19

leoluk opened this issue Jan 2, 2020 · 2 comments
Labels
enhancement New feature or request help-welcome

Comments

@leoluk
Copy link

leoluk commented Jan 2, 2020

Can isopod delete old resources that have been removed from the config?
@cxuu
Copy link
Contributor

cxuu commented Jan 2, 2020

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.

@cxuu cxuu added enhancement New feature or request help-welcome labels Jan 2, 2020
@uhthomas
Copy link

Is there a timeline on this sort of functionality? Would absolutely love to see it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request help-welcome
Milestone
No milestone
Development

No branches or pull requests
3 participants
@leoluk @uhthomas @cxuu