kubeval

kubeval copied to clipboard

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...

amnk

Hi, I have a YAML file containing multiple K8s resources. One of the resources contains `data` attribute with a config from a monitoring service. The config has multiple lines commented...

Jeiwan

Invalid `successThrehold` value in `livenessProbe` not caught

2

I'm not sure whether this can be fixed, as context is likely not something easily captured in the underlying JSON schemas… but apparently the `successThreshold` value must be set to...

orrc

Namespace name isn't validated

4

Thanks for this useful tool. I noticed Namespace names aren't validated. Here's my Namespace manifest. ```yaml apiVersion: v1 kind: Namespace metadata: name: example.com/dxia-test ``` ``` kubectl apply -f namespace.yaml error:...

davidxia

Compartmentalize gojsonschema Format types

2

This moves the ValidFormat type and its related functions out of the main package code. It also moves the calls to FormatCheckers.Add to an init function so as to only...

ian-howell

Wen ping a single file with many objects, would be nice that `kubeval` print the resource name, it would make much easier to find which one is failing.

rimusz

Multiple JSON via stdin only validates the first one

2

$ echo '{"kind":"Namespace","apiVersion":"v1","metadata":{"name":"test"}}\n{"kind":"Service","apiVersion":"v1","metadata":{"name":"test","namespace":"test"},"spec":{"ports":[{"name":"http","protocol":"TCP","port":80,"targetPort":80}],"selector":{"app":"test"},"type":"ClusterIP","sessionAffinity":"None"}}' | kubeval The document stdin contains a valid Namespace

tsjnsn

Docker image doesn't support glob syntax

2

### Description The docker image for kubeval doesn't expand glob syntax making it impossible to properly scan complex directory structures that have been mounted into the container. ### Expected Outcome...

jzelinskie

Kubeval doesn't work correctly with xargs

1

`kubeval` incorrectly reads from stdin when used with `xargs`. Here's an example: ``` $ echo "foo.txt" > files.txt $ xargs kubeval < files.txt standard input appears to be an empty...

ahawkins

For GitLab CI, it would be nice to force color output even if stdout is not a TTY.

bgagnon