This issue prevents the use of IngressRoute CRDs on Kubernetes 1.16 as there are no examples for the CRD definitions with the openAPIV3Schema attribute.

@msnelling That's not true. I'm using them on 1.16 and they work. Examples (without openAPIV3Schema) are in the docs and they still work in 1.16

@AndrewSav Really? I have just tried this on a fresh MicroK8s snap install on Ubuntu 18.04 with the following CRD.

apiVersion: apiextensions.k8s.io/v1
kind: CustomResourceDefinition
metadata:
  name: ingressroutes.traefik.containo.us

spec:
  group: traefik.containo.us
  versions:
    - name: v1alpha1
      served: true
      storage: true
  names:
    kind: IngressRoute
    plural: ingressroutes
    singular: ingressroute
  scope: Namespaced

I get the following error...

The CustomResourceDefinition "ingressroutes.traefik.containo.us" is invalid: spec.versions[0].schema.openAPIV3Schema: Required value: schemas are required

Version

Client Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.0", GitCommit:"2bd9643cee5b3b3a5ecbd3af49d09018f0773c77", GitTreeState:"clean", BuildDate:"2019-09-18T14:36:53Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.0", GitCommit:"2bd9643cee5b3b3a5ecbd3af49d09018f0773c77", GitTreeState:"clean", BuildDate:"2019-09-18T14:27:17Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"linux/amd64"}

@msnelling, well this what this github issue is about, they don't work in apiextensions.k8s.io/v1, just don't move them in that version and use the example from the doco verbatim,as I mentioned above. In this case they do work and will continue to work until kubernetes 1.19

Beyond the compatibility with the new version, it would be quite nice to have the openAPISchemas on the CRDs, so you can quickly kubectl explain them to figure out their fields.

Kubernetes 1.19 is slated to be out on 25th of August. This is the version that was going to remove apiextensions.k8s.io/v1beta1

Beyond the compatibility with the new version, it would be quite nice to have the openAPISchemas on the CRDs, so you can quickly kubectl explain them to figure out their fields.

... and to (hopefully) get support for the CRDs in the IntelliJ Kubernetes plugin!

removal has been retargeted at 1.22

This is my work in progress (manual) on this: https://gist.github.com/james-d-elliott/c3323ab66df3f09150b7538a8a8a8aca

Is anyone working on this? Or are there plans to automate it? If not I may do a PR with just the changes, including documenting some of the structs in pkg/provider/kubernetes/crd according to other struct tags found throughout the repo.

Additionally I'm running this in my cluster currently, however I only really use the Middleware and IngressRoute types.

Hello @james-d-elliott,

We have started to work on it.
Indeed, we will use code generation for the open schema API to facilitate the maintenance and upgrades.