[P1BIGROCKS-1380](https://jira.il2.dso.mil/browse/P1BIGROCKS-1380) There are many linting tools that would improve our reliability, consistency, and security posture for Kubernetes Objects. Additionally, we're not validating that the requirements for packages as outlined in the charter are being met. - [ ] [Istioctl](https://istio.io/latest/docs/ops/diagnostic-tools/istioctl-analyze/) - [ ] [get-istio](https://github.com/tetratelabs/getistio) - [ ] [Kube-Linter](https://github.com/stackrox/kube-linter) - [ ] [ClusterLint](https://github.com/digitalocean/clusterlint) - [ ] [Polaris](https://github.com/FairwindsOps/polaris) - [ ] [Helm Lint](https://helm.sh/docs/helm/helm_lint/) - [ ] [Goldilocks](https://github.com/FairwindsOps/goldilocks) - [ ] [PopEye](https://github.com/derailed/popeye) - [ ] [kube-score](https://github.com/zegl/kube-score) These tools should validate: - https://repo1.dso.mil/platform-one/big-bang/bigbang/-/blob/master/charter/PackageRequirements.md#pr-x-kubernetes-component-requirements - https://learnk8s.io/validating-kubernetes-yaml Use pre-commits to validate before pushing and running CI: - https://git-scm.com/book/en/v2/Customizing-Git-Git-Hooks - https://www.danilucaci.com/blog/how-to-lint-and-test-code-using-git-pre-commit-hooks These tools could/should be run - [ ] As part of package linting steps - [ ] After a package is deployed to CICD - [ ] After an install of BigBang in CICD