configuration file with wrong ident for readinessProbe recognized as valid for deployment

[az-esm]

in my case the readinessProbe was badly intended for 1 tab more that cause to deployment to fail. but kubeval mark the file as valid

[yannh]

Hi @az-esm , be sure to run kubeval with --strict : it should fail on this since they should detect an "unknown property". Can you confirm you run using --strict? Thanks!