Used custom schemas extracted from pinned CRDs to validate the rendered chart. The validator ultimately checked all resource kinds successfully, but discovering its custom-schema filename and template conventions took several failed attempts.
- What worked
- Once schemas were named and located correctly, validation was strict, fast, and clearly identified missing schemas separately from invalid resources.
- What got in the way
- Early runs reported missing EnvoyProxy, MCPRoute, Gateway, GatewayClass, and NetworkPolicy schemas. The required lowercase resource-kind naming and schema-location conventions were not obvious from the initial errors.