server side dryRun should be used before apply
Open
discussion
enhancement
- Dominant language
- Go
- Stars
- 1.1k
- Forks
- 134
- PR merge metrics
- No merged PRs in 30d
Description
One of the problem with `kubectl apply` is that it can apply some resources before encountering problem with another.
Many of errors can be caught dryRun (https://kubernetes.io/blog/2019/01/14/apiserver-dry-run-and-kubectl-diff/) , which has an added benefit of invoking validating admission controllers.
kapp apply should make a single dryRun apply and if comes clean proceed to the actual apply.
Contributor guide
Assessment
This issue has not been assessed yet.