Existing operator-framework/olm image is too old(3 years) and facing issue when trying to use latest image.

[cniket]

We have doc[1] for installing OLM support on an k8s cluster. The command to install the resources is as mentioned below;

$ kubectl apply -f https://raw.githubusercontent.com/operator-framework/operator-lifecycle-manager/master/deploy/upstream/quickstart/olm.yaml

The operator-framework/olm image used in the above olm.yaml is (v0.18.3) quay.io/operator-framework/olm@sha256:e74b2ac57963c7f3ba19122a8c31c9f2a0deb3c0c5cac9e5323ccffd0ca198ed , which is 3 years old now as per below screenshot;

When I tried to use the latest images with tag v0.28.0 or v0.27.0 , the pods that I get are;

❯ kubectl get pods -n olm
NAME                                READY   STATUS    RESTARTS   AGE
catalog-operator-58cbc4986b-ltzbp   1/1     Running   0          20m
olm-operator-64d5b6fdcf-dkbn8       1/1     Running   0          20m
operatorhubio-catalog-qk4rf         1/1     Running   0          20m
❯

Here the packageserver deployment and thus its pods are not getting created as shown in the .md link[1], however I get an operatorhubio-catalog pod as shown above which is not mentioned there in the link[1].

If we proceed to further install the forklift using below command as per link[2]

$ kubectl apply -f https://raw.githubusercontent.com/kubev2v/forklift/main/operator/forklift-k8s.yaml

Then I do not get forklift-operator pod, only below pods are generated

❯ kubectl get pods -n konveyor-forklift
NAME                                                              READY   STATUS      RESTARTS   AGE
a9bb8ee17fe994066840b424edfd5e203e266d02b5060139f27bbb96cfhxfsg   0/1     Completed   0          35s
konveyor-forklift-lkbtq                                           1/1     Running     0          52s
❯

❯ kubectl get deploy -n konveyor-forklift
No resources found in konveyor-forklift namespace.
❯

❯ kubectl get clusterserviceversion -A
NAMESPACE   NAME            DISPLAY          VERSION   REPLACES   PHASE
olm         packageserver   Package Server   0.27.0
❯

After that If ForkliftController CR is added as per link[3], then forklift-controller pod is not created. The pods remains same as shown above.

Everything mentioned in the doc happens if the yamls are applied as it is with old operator-framework/olm image of v0.18.3, however as that image is very old now(3 years) , we wish to deploy latest images.

Thus, how to get all this working with latest operator-framework/olm images? Can we please have the yamls and procedure updated that suite the latest images?

[1] https://github.com/kubev2v/forklift/blob/main/operator/docs/k8s.md#installing-olm-support

[2] https://github.com/kubev2v/forklift/blob/main/operator/docs/k8s.md#installing-latest

[3] https://github.com/kubev2v/forklift/blob/main/operator/docs/k8s.md#creating-a-forkliftcontroller-cr

[jsakil14]

Are you not using the bazel build method?