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.

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

Add a post-merge PR deployment cleanup script #1468

Open
bourgeoisor opened this issue Apr 26, 2023 · 1 comment
Open

Add a post-merge PR deployment cleanup script #1468

bourgeoisor opened this issue Apr 26, 2023 · 1 comment
Labels
priority: p3 Desirable enhancement or fix. May not be included in next release. type: process A process-related concern. May include testing, release, or the like.

Comments

@bourgeoisor
Copy link
Member

If the PR trigger fails to complete, it may leave a residual deployment namespace (with a running deployment) in the development cluster that will never be cleaned up. These can pile up over time. We should look into having a script (or trigger) that runs periodically and cleans up these namespaces.

@bourgeoisor bourgeoisor added type: process A process-related concern. May include testing, release, or the like. priority: p3 Desirable enhancement or fix. May not be included in next release. labels Apr 26, 2023
@bourgeoisor
Copy link
Member Author

Update: I just deleted hundreds of remnant PR namespaces. We should definitely look into this.

This is what I used:

for namespace in (k get ns -o name | grep pr)
    kubectl delete $namespace
end

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p3 Desirable enhancement or fix. May not be included in next release. type: process A process-related concern. May include testing, release, or the like.
Projects
None yet
Development

No branches or pull requests

1 participant