Add support for Istio resources

[grebois]

Considering this resource:

---
apiVersion: config.istio.io/v1alpha2
kind: RouteRule
metadata:
  name: default-pipeline-service
spec:
    destination:
      name: default-pipeline-service
    match:
        request:
          headers:
            uri:
              prefix: /api/
    rewrite:
        uri: /
---

I get:

2 errors occurred:

* Problem loading schema from the network at https://raw.githubusercontent.com/garethr/kubernetes-json-schema/master/master-standalone/routerule.json: Could not read schema from HTTP, response status is 404 Not Found
* Missing a kind key

This is the API reference: https://istio.io/docs/reference/config/istio.networking.v1alpha3/

[ror6ax]

I'd be interested to work on this.

[garethr]

There are some details in #47 as well. This should just require generating the JSON Schemas from the Istio OpenAPI docs (I use https://github.com/garethr/openapi2jsonschema) and then including them in the right location. If someone can point me at the openapi description for Istio I might be able to add better support for CRDs in kubeval.

[tmc]

Is it possible to hit a dynamic resource for this? As I do more CRD work (and work with knative, etc.) running a 'kubectl proxy' and hitting the /api endpoints there would be pretty fantastic..

[garethr]

@tmc yes, at least theoretically. The problem there is you can only test against that specific version of the schema, and you need a server running to run the tests - which might be OK depending on your use case.

[Justin2997]

@garethr Any update on this ? Can I help ?

[Justin2997]

For people that will like Istio or other CRD like Knative I subject that skip validation for specific apiVersion that you pass to your script before running KubeVal.

[grzesuav]

hi @garethr , in general it would be useful to have possibility to add additional schemas (alongside k8s one's) - how I can see it, it could be via config file, when location for additional schemas could be placed. What do you think of it ?

My use case :

• we use additional k8s components
• we write own's CRD's

cheers

[Stono]

So we can't run kubeval if there is a CRD in the helm template, it'd be great to add an --ignore-unknown-apis or something similar please!

[garethr]

I'm going to close this as:

1. a duplicate of cannot validate CustomResourceDefinitions #47, Istio resources are really just specific custom resources
2. You can now at least ignore missing schemas with --ignore-missing-schemas in 0.11.0