-
Kubeval is thowing an error on try to validate a yaml file
ERR - delivery/deployment.yaml: Failed initializing schema https://kubernetesjsonschema.dev/master-standalone/podmonitor-monitoring-v1.json…
-
$ echo '{"kind":"Namespace","apiVersion":"v1","metadata":{"name":"test"}}\n{"kind":"Service","apiVersion":"v1","metadata":{"name":"test","namespace":"test"},"spec":{"ports":[{"name":"http","protoc…
-
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 `1`, if used withi…
-
Any chance you could provide a zip URL of all the schemas for us behind corporate firewalls?
Or maybe bake all the schemas into a second docker image?
-
Example. kubeval indicated that my yaml is valid. kubctl did not complain when applying it, except pods were not created. The yaml contained a container port name longer than 15 characters which is no…
-
So it's clear what version is being used.
-
Getting an invalid Deployment when validating custom resources using kubeval with the additional CRD schemas. The `seccomp` profile feature was shipped in Kubernetes 1.19, is this not supported yet?
…
muram updated
2 years ago
-
```yaml
kind: Pod
metadata:
name: demo
labels:
role: myrole
spec:
containers:
- name: bad_name
```
```
a DNS-1123 label must consist of lower case alphanumeric characters or…
-
We can do deep validation, but perhaps using the API schema is doable, or kubeval may be a nicer option.
Also, kubetest hooks could be built-in.
cc @garethr
-
I keep getting this error:
```
Failed initializing schema https://kubernetesjsonschema.dev/master-standalone/statefulset-apps-v1.json: read tcp xxxxxxxx->xxxxxxxx: read: connection reset by peer
…