-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Perform cleanup during development or on exit #61
Labels
area/deploy
kind/feature-request
priority/p3
agreed that this would be good to have, but no one is available at the moment.
Comments
Would be good to consider the UX when the remote registries (e.g. GCR) are used. |
dgageot
added a commit
to dgageot/skaffold
that referenced
this issue
Apr 18, 2018
Fix GoogleContainerTools#61 Signed-off-by: David Gageot <[email protected]>
dgageot
added a commit
to dgageot/skaffold
that referenced
this issue
Apr 20, 2018
Fix GoogleContainerTools#61 Signed-off-by: David Gageot <[email protected]>
Not yet finished! |
r2d4
added
the
priority/p3
agreed that this would be good to have, but no one is available at the moment.
label
Jul 1, 2018
@dgageot what else needs to be done here? |
@nkubala image pruning is not done but we could create a new issue for that |
Closed
This was referenced Jan 9, 2019
Closed
Let's close this one since #733 is here to implement pruning |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/deploy
kind/feature-request
priority/p3
agreed that this would be good to have, but no one is available at the moment.
This is an umbrella issue for some ideas on how we might clean up the development artifacts we create in a
skaffold dev
pipeline.The text was updated successfully, but these errors were encountered: