Skip to content

Is there a rule of thumb, which errors kubeconform will find? #341

Description

@kastl-ars

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

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions