Closed jkremser closed 5 years ago
/assign tnozicka
Interesting, I know the deprecated legacy (non groupified) API got dropped in 4.x but we were running our CI against 4.0 and today I have tried running the CI with OCP 4.1 and 4.2 and it still got over the resource creation https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/pr-logs/pull/openshift_release/4245/rehearse-4245-pull-ci-tnozicka-openshift-acme-master-e2e-cluster-wide/2
clusterrole.rbac.authorization.k8s.io/openshift-acme added: "openshift-acme"
so I wonder maybe you have an older oc client? maybe the new one automatically converts those to new resources.
I have a fix in https://github.com/tnozicka/openshift-acme/pull/97 but I was hoping to see it first fail against OCP 4.x so I could verify it fixes the issue.
yes, the obsolete oc client may have been the cause, I bumped later on to similar issue (on different domain) and using the 4.x client worked. It's weird though, I always though the client is pretty dumb when it comes to API and doing some magic under the cover w/ the payloads.
yeah, apparently that was the middle ground for removing legacy /oapi
In OCP 4.0 and since a corresponding version of K8s the
apiVersion
s of image stream and cluster role have changed.for image streams, it's: v1 -> image.openshift.io/v1
for cluster role, it's: v1 -> rbac.authorization.k8s.io/v1
Otherwise the creation of those resources fail with: