Schema validation silently fails for non-existent Kubernetes version about kubeconform

[yannh]

Hi @Niksko , this seems to work as expected? If you ignore missing schemas, it will skip resources for which it doesnt find a shema - in this case all of them. If you do not pass -ignore-missing-schemas, it will error when it doesnt find a schema for a resource - in this case for all of them...

I would recommend you use -skip to explicitly ignore the kinds for which you know you do not have a schema, so that you don't get these silent errors as when using -ignore-missing-schemas.

[yannh]

I will close this since it is working as expected - a Kubernetes version missing should trigger a "schema not found" - I can't get kubeconform to fail on it, since you might be specifying multiple schema locations... I hope you found a way to get this to work with -skip :)