Dear Yann,
we stumbled upon a behaviour in kubeconform which we do not fully understand.
Say we have a deployment.yaml that contains a typo. We mistyped spec: and have written specDOESNOTEXIST: instead.
kubeconform does not complain and says the deployment is valid.
cat deployment.yaml| kubeconform -summary
Summary: 1 resource found parsing stdin - Valid: 1, Invalid: 0, Errors: 0, Skipped: 0
However it catches an error where the number of replicas is given as a string, not an integer.
Shouldn't the specDOESNOTEXIST error be found? spec is mandatory in a deployment, at least that is what I thought. Is this simply not in the schema for deployment?
Thanks for the clarification!
Kind Regards,
Johannes
Dear Yann,
we stumbled upon a behaviour in kubeconform which we do not fully understand.
Say we have a
deployment.yamlthat contains a typo. We mistypedspec:and have writtenspecDOESNOTEXIST:instead.kubeconform does not complain and says the deployment is valid.
However it catches an error where the number of replicas is given as a string, not an integer.
Shouldn't the
specDOESNOTEXISTerror be found?specis mandatory in a deployment, at least that is what I thought. Is this simply not in the schema for deployment?Thanks for the clarification!
Kind Regards,
Johannes