GoogleContainerTools / GoogleContainerTools/skaffold
Skaffold deployment do not store CHANGE-CAUSE to rollout
- Dominant language
- Go
- Stars
- 15.9k
- Forks
- 1.7k
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 10
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](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#checking-rollout-history-of-a-deployment)
### Actual behavior
```
kubectl rollout history deployment/api-n production
```
```
REVISION CHANGE-CAUSE
74
75
76
77
78
```
### 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
Assessment
This issue has not been assessed yet.