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