kustomize-resource-validation

To validate kustomization.yaml references, you can check that all resource and patch files exist and are well-formed. This process detects missing references and malformed patches early to prevent runtime failures in your Kubernetes configurations.

Finding orphaned files in a kustomize directory involves identifying YAML files present in the folder that are not referenced in kustomization.yaml. This orphan file detection ensures every configuration file is actively managed and deployed.

Checking cross-environment consistency for kustomize overlays compares resource and patch lists across different environments for discrepancies. This comparison ensures configurations remain synchronized and consistent across your deployment targets.

Yes, you can verify secretGenerator and configMapGenerator entries in kustomize configurations. This validation checks generator definitions and optional settings like disableNameSuffixHash to ensure they are correctly configured before deployment.

Yes, kustomize build validation attempts to build the configuration with kustomize build to verify correctness. Running this in CI/CD pipelines catches configuration issues early, preventing deployment failures and ensuring reliability.