Hello, I’m using the Kong Ingress Controller and noticed that the CRDs in both the helm chart and ingress controller repo are using the
apiextensions.k8s.io/v1beta1 apiVersion. Kubernetes 1.16 introduced a
apiextensions.k8s.io/v1 apiVersion that requires structural schemas. This provides validation support to custom resources, so we could add a “dry run” to our CI pipeline that ensures our KongIngress resources are valid without having to actually apply them to kube-apiserver. Additionally, the existing v1beta1 apiVersion optionally supports structural schemas as well as mentioned earlier in that last link.
Could the existing CRDs be updated to have structural schema and perhaps provide opt-in support for the v1 CRD API in the helm chart?