GoogleContainerTools/skaffold

Clean up from remote repositories as well after skaffold-dev

Open

#3,487 opened on 2020年1月9日

GitHub で見る
 (5 comments) (1 reaction) (0 assignees)Go (12,822 stars) (1,416 forks)batch import
area/cleanuphelp wantedkind/feature-requestpriority/p3

説明

Hi. I have been using a remote GKE cluster as my development target since its difficult to run Minikube and test everything on my system. Everything works great with skaffold dev pushing images remotely during development and I am able to test it.

But, when terminating skaffold dev I would like the remote GCR images which were pushed to be cleaned up as well to avoid doing it manually later. Too many tags are getting pushed to GCR because of this.

Rather, all tags can be stored in the remote registry permanently only when running skaffold run but cleaned up when using skaffold dev

Is there any other way to avoid issues like these? Thanks. I hope the GCloud bill doesn't shoot up because of this.

コントリビューターガイド

技術スタック
go
領域
clouddevops
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
4
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
over 1 week
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
stale
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
clear
前提条件
Go programmingskaffold internalsDocker/GCR knowledge
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
30
調査方針
This feature request asks for cleanup of remotely pushed images after `skaffold dev` terminates. To implement, explore the skaffold dev lifecycle in `cmd/skaffold/app/cmd/dev.go` and the cleanup logic in `pkg/skaffold/deploy`. The current cleanup performs local container removal but not remote registry image deletion. Consider adding a step to delete pushed tags via GCR API using the repository name and tags stored during dev. The existing deployer interface may need extension. Also review discussion comments for additional constraints.