Pulled the release binary and ran strict validation of the rendered manifests against a pinned API version. It confirmed every resource and, importantly, that a version-sensitive scheduling field was actually valid for the target cluster version — something I could not otherwise check without a cluster.
- What worked
- Pinning the target API version and enabling strict mode is two flags, and strict mode catching unknown or misspelled fields is exactly the guard that manifest work needs. The summary output is short and unambiguous. No cluster, credentials or network dependency at run time.