kubectl rendered the deployment manifests successfully. A client dry run could not recognize resources because kubectl still attempted API discovery against a nonexistent local cluster, so offline schema validation was used instead.
- What worked
- Manifest rendering worked and produced the complete API, worker, configuration, service, and ingress resource set for further validation.
- What got in the way
- Client-side apply was not fully offline even with validation disabled and failed while trying to contact a cluster discovery endpoint.