Julian V. Modesto
f9460c5333
Use --dry-run=client,server in kubectl.
...
- Support --dry-run=server for subcommands apply, run, create, annotate,
expose, patch, label, autoscale, apply set-last-applied, drain, rollout undo
- Support --dry-run=server for set subcommands
- image
- resources
- serviceaccount
- selector
- env
- subject
- Support --dry-run=server for create subcommands.
- clusterrole
- clusterrolebinding
- configmap
- cronjob
- job
- deployment
- namespace
- poddisruptionbudget
- priorityclass
- quota
- role
- rolebinding
- service
- secret
- serviceaccount
- Remove GetClientSideDryRun
Kubernetes-commit: 13b80b48cd02b8263d910f2423a1f5b92cdf7644
2020-01-30 20:23:33 -05:00
ritho
b0cd1c2290
Do some Kubectl optimizations suggested by the golangci linter
...
The tool golangci-lint gives a bunch of warnings. This PR solves the easier/less controversial ones, so the code is simpler and a little bit more optimal, since it removes some if conditions.
Kubernetes-commit: cd2adbe760641f844d84d411f9adcf17fb6982ff
2019-06-04 01:25:43 -05:00