3 ms·
Would be nice to have a linter or something that you know is best practice. Eg if you check your yaml and its more complex than it could be.
by x87678r 6y ago
Would be nice to have a linter or something that you know is best practice. Eg if you check your yaml and its more complex than it could be.
- programd 6y agoThere are a number of such tools out there. Here's a short list. I'd be interested in any experiences people have had with them in largish production environments. https://www.kubeval.com/ https://www.kubeval.com/ https://github.com/zegl/kube-score https://github.com/zegl/kube-score https://stelligent.github.io/config-lint/#/ https://stelligent.github.io/config-lint/#/ https://github.com/cloud66-oss/copper https://github.com/cloud66-oss/copper https://www.conftest.dev/ https://www.conftest.dev/ https://github.com/FairwindsOps/polaris#cli https://github.com/FairwindsOps/polaris#cli
- zegl 6y agoHey, I'm the author of kube-score, and originally built the tool to support an organization using Kubernetes at a fairly large scale as measured in number of engineers, services, and Kubernetes clusters. I'm obviously biased, but it's been hugely successful! kube-score is working very well out of the box, and there's only a handful of cases where the "ignore" annotation has been used to disable a check that's too strict for the particular use case. Feel free to reach out if you have any questions or comments.