no matches for kind CustomResourceDefinition about cert-utils-operator

[slaterx]

Further to this, v0.1.0 instead of v0.1.1 works fine after deploying.

[raffaelespazzoli]

CustomResourceDefinition are typically defined in each kube environment. In which environment are you running?

[devopstales]

openshift OKD 3.11 If I try by command line it can be found:

oc get CustomResourceDefinition.apiextensions.k8s.io
NAME                                  CREATED AT
certificaterequests.cert-manager.io   2020-06-14T09:09:47Z
certificates.cert-manager.io          2020-06-14T09:09:47Z
challenges.acme.cert-manager.io       2020-06-14T09:09:46Z
clusterissuers.cert-manager.io        2020-06-14T09:09:46Z
issuers.cert-manager.io               2020-06-14T09:09:47Z
orders.acme.cert-manager.io           2020-06-14T09:09:47Z

[raffaelespazzoli]

can you look at the version of the crd object?
oc get CustomResourceDefinition.apiextensions.k8s.io certificaterequests.cert-manager.io

[slaterx]

@raffaelespazzoli I can reproduce the error above. I'm also running OKD 3.11.

Running your command gives me:

oc get CustomResourceDefinition.apiextensions.k8s.io certificaterequests.cert-manager.io
NAME                                  CREATED AT
certificaterequests.cert-manager.io   2020-06-14T20:45:53Z

[raffaelespazzoli]

sorry I should have been clearer. can you run this command:oc get CustomResourceDefinition.apiextensions.k8s.io certificaterequests.cert-manager.io -o yaml
and look at the apiversion of the CustomResourceDefinition type. I'm going to guess it's not v1 in OKD 3.11.

[slaterx]

Correct, it is v1alpha2:

oc get CustomResourceDefinition.apiextensions.k8s.io certificaterequests.cert-manager.io -o yaml
(...)
apiVersion: apiextensions.k8s.io/v1beta1
kind: CustomResourceDefinition
metadata:
(...)
  name: certificaterequests.cert-manager.io
  selfLink: /apis/apiextensions.k8s.io/v1beta1/customresourcedefinitions/certificaterequests.cert-manager.io
(...)
  version: v1alpha2
  versions:
  - name: v1alpha2
    served: true
    storage: true
status:
(...)
  storedVersions:
  - v1alpha2

[raffaelespazzoli]

ok, I have no plan to maintain backward compatibility with the 3.x line of OpenShift. So, I think you have three options:

1. run the v0.1.0 version of the operator
2. upgrade to OpenShift 4.x
3. fork the operator and backport it to OpenShift 3.x

[slaterx]

Will you consider our PR if we find a way to backport it?

[raffaelespazzoli]

@slaterx sure.
I assume the CRD injection is not something that makes much sense anyway on OpenShift 3.11, so perhaps the best approach for this patch would be to simple disable that controller when running on OpenShift 3.x

[raffaelespazzoli]

@slaterx may I close this issue?

[slaterx]

Yes, you can close it @raffaelespazzoli!