As a workaround, I was able to add this to the CRD definition to create it on recent Kubernetes versions:
validation: openAPIV3Schema: type: object x-kubernetes-preserve-unknown-fields: true
This does happen to fix the issue that I encountered. However, if an upstream service were to attempt to list the CRDs themselves (as opposed to the custom resources), it would fail due to the apiVersion not matching.
As a workaround, I was able to add this to the CRD definition to create it on recent Kubernetes versions:
validation: hema: kubernetes- preserve- unknown- fields: true
openAPIV3Sc
type: object
x-
This does happen to fix the issue that I encountered. However, if an upstream service were to attempt to list the CRDs themselves (as opposed to the custom resources), it would fail due to the apiVersion not matching.