When -kubernetes-version=X.Y (and not X.Y.Z) is provided, kubeconform cannot find schema even for built-in resources

[PawelLipski]

Version: v0.4.13

Smallest repro:

cat > foo.yaml <<EOF
apiVersion: v1
kind: ConfigMap
metadata:
  name: foo
data: {}
EOF

$ kubeconform -kubernetes-version=1.20 foo.yaml
foo.yaml - ConfigMap foo failed validation: could not find schema for ConfigMap

$ kubeconform -kubernetes-version=1.20.0 foo.yaml && echo OK
OK

The error should be something more clear, like just specify kubernetes-version as X.Y.Z rather as X.Y.

[yannh]

Hi @PawelLipski , indeed the kubernetes version need to be x.y.z and something present in this repo https://github.com/yannh/kubernetes-json-schema . We could do some increased validation of the value to fail earlier.