Skaffold deployment do not store CHANGE-CAUSE to rollout

(2 則留言) (0 個反應) (0 位負責人)Go (1,416 個分叉)batch import

help wantedkind/feature-requestpriority/p2

倉庫指標

星標: (12,822 顆星)
PR 合併指標: (平均合併 3天 6小時) (30 天內合併 16 個 PR)

描述

Expected behavior

Skaffold should save the kubectl command that is making changes to the resource. This is done by the --record flag. More information: checking-rollout-history-of-a-deployment

Actual behavior

kubectl rollout history deployment/api-n production

REVISION  CHANGE-CAUSE
74        <none>
75        <none>
76        <none>
77        <none>
78        <none>

Information

Skaffold version: 1.13.0
Operating system: Windows

Steps to reproduce the behavior

Deploy a sample app
Run kubectl rollout history deployment/your-app

貢獻者指南

研究方向: 檢查 Skaffold 中執行 `kubectl apply` 的部署程式碼，並新增 ` record` 標誌以在 rollout 歷史中保留 CHANGE CAUSE。
技術棧: go
領域: infrastructuredevops
議題類型: 錯誤
難度: 2
預計時間: 1-3 小時
活動狀態: 活躍
清晰度: 清晰
前置要求: Kubernetes
新手友善度: 75