GoogleContainerTools/skaffold

Skaffold deployment do not store CHANGE-CAUSE to rollout

Open

#4,667 opened on Aug 14, 2020

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Go (1,416 forks)batch import
help wantedkind/feature-requestpriority/p2

Repository metrics

Stars
 (12,822 stars)
PR merge metrics
 (Avg merge 3d 6h) (16 merged PRs in 30d)

Description

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

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

Contributor guide

Research direction
Inspect the Skaffold deployer code that runs `kubectl apply` and add the ` record` flag to preserve CHANGE CAUSE in rollout history.
Tech stack
go
Domain
infrastructuredevops
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Kubernetes
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75