Comment 2 for bug 1910820

I can confirm that using the non-beta v1 k8s API does allow a pod spec with this CRD to be deployed. Since there's only one version entry, you can easily adjust the CRD to conform to the beta1 syntax to get things working with juju 2.8

  customResourceDefinitions:
    - name: certificates.networking.internal.knative.dev
      spec:
        scope: Namespaced
        group: networking.internal.knative.dev
        names:
          kind: Certificate
          plural: certificates
          singular: certificate
          categories:
            - knative-internal
            - networking
          shortNames:
            - kcert
        versions:
          - name: v1alpha1
            served: true
            storage: true
            subresources:
              status: {}
            schema:
              openAPIV3Schema:
                type: object
                # this is a work around so we don't need to flush out the
                # schema for each version at this time
                #
                # see issue: https://github.com/knative/serving/issues/912
                x-kubernetes-preserve-unknown-fields: true
            additionalPrinterColumns:
              - name: Ready
                type: string
                jsonPath: ".status.conditions[?(@.type==\"Ready\")].status"
              - name: Reason
                type: string
                jsonPath: ".status.conditions[?(@.type==\"Ready\")].reason"