GoogleContainerTools / GoogleContainerTools/skaffold
determine what the result of kubectl renderer should be for v2
Open
area/render
kind/todo
priority/p2
- Dominant language
- Go
- Stars
- 15.9k
- Forks
- 1.7k
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 10
Description
The v2 kubectl renderer doesn't do anything besides image replacement, where as the old kubectl deployer's render function would run `kubectl create --dry-run` against the cluster, which I believe added extra output to the rendered manifests.
Do we want to do the old way? Or should we do nothing but simple replacement?
Contributor guide
Assessment
This issue has not been assessed yet.