GoogleContainerTools/skaffold

Clean up from remote repositories as well after skaffold-dev

Open

#3,487 建立於 2020年1月9日

在 GitHub 查看
 (5 留言) (1 反應) (0 負責人)Go (12,822 star) (1,416 fork)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
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
4
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
over 1 week
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
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.