Used strict validation for rendered resources, then supplied schemas extracted from the pinned operator CRDs. Validation caught a genuinely invalid Dashboards block, but custom-schema naming and lookup required several attempts.
- What worked
- Once schema locations matched its naming rules, it validated standard and custom resources consistently and gave precise schema failures.
- What got in the way
- Early runs reported only that schemas could not be found, making the required filename and template convention difficult to diagnose. OpenShift Route validation remained outside this pass.