This repository has been archived by the owner on Feb 14, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 115
Package and Registry Resources not Deleted upon app deletion #671
Labels
Comments
We have created an issue in Pivotal Tracker to manage this: https://www.pivotaltracker.com/story/show/178514708 The labels on this github issue will be updated when the story is started. |
Update:
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Deleting an app should delete all the related data and routes:
Data includes Packages stored in minio blob storage, container images in Docker Registry
I have been using cf-for-k8s to deploy development workloads. There are times developers will create delete and recreate app to troubleshoot, or to just have a fresh start.
The packages uploaded for an app are not accessible once its deleted and recreated, cf starts a whole new upload for packaged zip.
This certainly is not an issue but the package data from previous deployment of the same app isn't deleted from blob store, this is leading to serious storage issues, especially when using private object storage and registry
Even my dockerhub account is populated with so many images from the app guids that don't exist anymore.
The resources being stored and named with long app guid are difficult to identify and delete manually.
Application Lifecycle Management Must destroy all the resources, with deletion of app.
Or a cleanup task should be there to cleanup dangling resources for apps(guids) that don't exist anymore
The text was updated successfully, but these errors were encountered: