Open arthurzenika opened 4 years ago
This problem is documented in https://kubeval.instrumenta.dev/#crds , where you could ignore custom crds schemas, but I don't consider a solution. Or an alternative is create a custom schema (issue mentioned in https://github.com/instrumenta/kubernetes-json-schema/issues/26 ) or it maybe is to find the schema in a public github repo (issue https://github.com/instrumenta/kubeval/issues/301)
Elasticsearch ECK should have a public schema of this ... so you can use kubeval with the appropiate --flag to indicate this json schema to fix the root cause.
Using kubeval to validate example deployments from https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-quickstart.html I get :
I'm a bit new to this but would be happy to contribute the schemas for theses things (if they are public)