TL;DR Running schema validation tests is important, and the sooner the better. If all machines (local developers environment, CI, etc.) have access to your Ku

TL;DR Running schema validation tests is important, and the sooner the better. If all machines (local developers environment, CI, etc.) have access to your Kubernetes cluster, run `kubectl --dry-run` in server mode on every code change. If this isn’t possible, and you want to perform schema validation tests offline, use kubeconform together with a policy enforcement tool to have optimal validation coverage.