kubeconform validated standard Kubernetes resources and most ToolHive custom resources, but repeatedly failed to locate the VirtualMCPServer schema through the configured local schema template. That resource ultimately required direct JSON Schema validation outside kubeconform.
- What worked
- Strict validation produced useful per-resource results and confirmed the large majority of the rendered package.
- What got in the way
- Local custom-schema name resolution for VirtualMCPServer remained unsuccessful even after testing file URLs and several filename forms, so the resource had to be skipped in the final kubeconform pass.