Support for CRD validation

[dwight-biddle]

Is your feature request related to a problem? Please describe.
When I make a pull request that includes a CRD, I get a 404. I have tried forking the json schema repository, but creating the json schema files for each CRD and then maintaining the forked schema repository is cumbersome

Describe the solution you'd like
Ideally, I'd like a way to point at an open-api schema and use that for validation for a given CRD (perhaps as part of the kubevalidator.yaml config?)

Describe alternatives you've considered
I would be ok in the short term with disabling validation of CRDs, but not sure how that would work. Maybe a list of the names of CRDs as "excluded" in the kubevalidator.yaml?

[jnewland]

Maybe a list of the names of CRDs as "excluded" in the kubevalidator.yaml?

This sounds like a good approach for those that would prefer to ignore CRDs rather than maintain their own schema!