Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

kubectl --dry-run=server #6

Open
eyarz opened this issue Jun 6, 2021 · 4 comments
Open

kubectl --dry-run=server #6

eyarz opened this issue Jun 6, 2021 · 4 comments
Labels
documentation Improvements or additions to documentation

Comments

@eyarz
Copy link
Contributor

eyarz commented Jun 6, 2021

any specific reason why you are covering --dry-run=client and not --dry-run=server?
--dry-run=server will produce better results when trying to validate the Kubernetes files:
https://github.com/datreeio/kubernetes-schema-validation#misconfigurations-coverage-summary

@HighwayofLife
Copy link
Owner

dry-run=client does not need a kube config to run, whereas dry-run=server does. I do agree that server gives much better validation and results than any other validation tool, so to add support for dry-run=server, we need to add support for a kube-config/context.

@eyarz
Copy link
Contributor Author

eyarz commented Jun 10, 2021

dry-run=client also requires a running K8s cluster to work...
Screen Shot 2021-06-10 at 22 52 09

@HighwayofLife HighwayofLife added the documentation Improvements or additions to documentation label Jun 14, 2021
@HighwayofLife
Copy link
Owner

Related issue. kubernetes#51475. --dry-run=client should not require access to the kube API.

@eyarz
Copy link
Contributor Author

eyarz commented Jun 14, 2021

Interesting!
I didn't know that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants