Closed MitchLillie closed 6 years ago
@MitchLillie could you try running Kubeval with the --strict
flag and report back if that resolves your issue? The Kubernetes API is actually completely fine with you sending unknown properties, however kubectl
layers on top of that some additional behaviour.
I'll close this issue for now, as I think strict
should work for what you're trying to do.
To reproduce:
Create a deployment.yml with the following:
Run
kubeval deployment.yml
The document deployment.yml contains a valid Deployment
Expected:
---> spec.type: Unknown property.
Or something along those lines