Open ms-choudhary opened 1 year ago
If I'm correct, OKD 4.6.0 matches Kubernetes 1.19. Kubernetes supports the three latest minors, which at the time of writing is 1.26, 1.25, 1.24. The api batch/v1beta1 was deprecated in 1.25 and batch/v1 was available from v1.21 (which seems to be OKD 4.8.0).
So the simplest way forward for you would be to upgrade your OKD to a recent version, which will also fix a number of security issues for you. The current OKD version is 4.12.0.
There are probably other ways forward as well, for example by forcing an older version of the operator from the operator hub and disabling automatic update, but in my opinion you should stay on top of the OKD/Openshift versions.
seems this can be closed?
Describe the bug Installed the argocd-operator using the console on OKD 4.6.0. The version installed is v0.4.0. The operator seems to be crashlooping with error:
To Reproduce Steps to reproduce the behavior:
Expected behavior Operator is healthy
Additional context On the current cluster, latest version of CronJob is batch/v1beta1, but operator seems to be using v1. How do I fix this?