kubeval icon indicating copy to clipboard operation
kubeval copied to clipboard

[question] Environment variables are not checked

Open amnk opened this issue 4 years ago • 0 comments

First of all - thanks for the great project.

I've tried using it in my pipelines, and things work so far. But I've noticed that incorrect environment variables are not detected, while helm upgrade fails with proper error message. For example, if I have 999Test env variable defined, I'd get: spec.template.spec.containers[0].env[4].name: Invalid value: "999Test": a valid environment variable name must consist of alphabetic characters, digits, '_', '-', or '.', and must not start with a digit (e.g. 'my.env-name', or 'MY_ENV.NAME', or 'MyEnvName1', regex used for validation is '[-._a-zA-Z][-._a-zA-Z0-9]*')

According to the spec, name is just a string, so I'm not sure such checks are even possible with kubeval, thus [question].

amnk avatar Oct 23 '19 22:10 amnk