You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For a Kubernetes Dashboard spec, also downloaded, the k8s API happily accepts this:
spec:
containers:
<...>
args:
# Uncomment the following line to manually specify Kubernetes API server Host
# If not specified, Dashboard will attempt to auto discover the API server and connect
# to it. Uncomment only if the default does not work.
# - --apiserver-host=http://my-address:port
Kubeval, however, doesn't like it:
The document ../../contentful/cf-infra-stacks/kubeconfigs/staging/us-east-1/delivery-k8s-002/kubernetes-dashboard/dashboard.yaml is not a valid Deployment
--> spec.template.spec.containers.0.args: Invalid type. Expected: array, given: null
The text was updated successfully, but these errors were encountered:
If Kubernetes accepts this it should instead be described as:
"type": [ "array", "null" ]
I'll post something to SIG API Machinery and see if this is correct. If so I'll file an upstream bug and also in the meantime splice this into the generated schemas.
So, the use of protocol buffers in Kubernetes means that it can't distinguish between null and empty arrays. And OpenAPI 2.0 doesn't support multiple types as shown in the comment above. Tracking this for upstream in the linked issue, which also has more context.
For a Kubernetes Dashboard spec, also downloaded, the k8s API happily accepts this:
Kubeval, however, doesn't like it:
The text was updated successfully, but these errors were encountered: