openshift / ovirt-csi-driver-operator Goto Github PK

I am running rke2 cluster and tried to deploy ovirt-csi-driver-operator.
I followed "Manual Installation" installation and hit various issues.

1. /manifests is missing rbac ovirt-kube-rbac-proxy-role which is defined in ovirt-csi-driver-operator/assets/rbac/ thus I had to apply kube_rbac_proxy_role.yamlandkube_rbac_proxy_binding.yaml`

2. for some reason ${DRIVER_IMAGE} is empty and I had to populate it.

3. looks like lates operator require also ${KUBE_RBAC_PROXY_IMAGE}.

It looks like Manual Install manifest is not up2date and needs corrections. Can you fix it please?

If someone interested I finally I made it work in rke2 cluster with some hacks.

• create credential secret
• create tls secret for metrics
• create storage class
• fix missing values of variables ${DRIVER_IMAGE} and ${KUBE_RBAC_PROXY_IMAGE}
• adjust nodeSelector to by able Schedule PODs

Can this driver be used and installed on native kubernetes, when starting the pod it tries to look form some openshift components/resources and fails to start

I installed this operator on an OKD 4.5 cluster running on RHV 4.3. I have three workers, and on two of them, the ovirt-csi-driver-node pods are crashlooping with an error listening on 8080:

I0807 18:35:58.891993       1 request.go:538] Throttling request took 2.769212846s, request: GET:https://172.30.0.1:443/apis/nodemaintenance.kubevirt.io/v1beta1?timeout=32s
I0807 18:35:58.941980       1 request.go:538] Throttling request took 2.81920033s, request: GET:https://172.30.0.1:443/apis/whereabouts.cni.cncf.io/v1alpha1?timeout=32s
I0807 18:35:58.991957       1 request.go:538] Throttling request took 2.869179948s, request: GET:https://172.30.0.1:443/apis/snapshot.kubevirt.io/v1alpha1?timeout=32s
F0807 18:35:58.999725       1 ovirt-csi-driver.go:62] error listening on :8080: listen tcp :8080: bind: address already in use

I tried rebooting my worker nodes, and following the reboot, one of these pods managed to come up on its worker. No idea if that reboot resolved anything or if it was incidental...

The following branches are being fast-forwarded from the current development branch (master) as placeholders for future releases. No merging is allowed into these release branches until they are unfrozen for production release.

• release-4.8
• release-4.9

Contact the Test Platform or Automated Release teams for more information.

The following branches are being fast-forwarded from the current development branch (release-4.15) as placeholders for future releases. No merging is allowed into these release branches until they are unfrozen for production release.

• release-4.17

For more information, see the branching documentation.

Is it possible to define multiple ovirt engine access from some different ovirt-credentials?
I've been able to define and apply a ovirt-credentials-2 manifest, but what am I supposed to do to make a new credential request?