Maxime Chambreuil

Other information: I am using OKD 4.5 on Fedora CoreOS 31. The pod `csi-do-controller-0` remains in status `CrashLoopBackOff`. 4 out of 5 containers are in state `Running` but have this...

Hello @timoreimann Yes I am running on droplets built from a custom image: Fedora CoreOS 31 for Digital Ocean from https://getfedora.org/en/coreos/download?tab=cloud_operators&stream=stable Yes, I can connect to the metadata endpoint from...

So I ran: ``` oc delete -f https://raw.githubusercontent.com/digitalocean/csi-digitalocean/master/deploy/kubernetes/releases/csi-digitalocean-v0.3.0.yaml oc apply -f https://raw.githubusercontent.com/digitalocean/csi-digitalocean/master/deploy/kubernetes/releases/csi-digitalocean-v1.3.0.yaml ``` I don't know if it helps but the container created from the DaemonSet is working fine on...

Even after running: ``` oc delete -f https://raw.githubusercontent.com/digitalocean/csi-digitalocean/master/deploy/kubernetes/releases/csi-digitalocean-v0.3.0.yaml ``` ?

@timoreimann Installing the cluster was a pretty painful process I would like to avoid. I removed all the `csi*` images from all the masters and workers: ``` podman image rm...

@timoreimann I deleted them. No errors when running: ``` kubectl apply -f https://raw.githubusercontent.com/digitalocean/csi-digitalocean/master/deploy/kubernetes/releases/csi-digitalocean-v1.3.0.yaml ``` Still the same behavior on the controller, i.e the pod csi-do-controller-0 remains in status CrashLoopBackOff. 4...

@timoreimann With @lucab and @dustymabe help, I got it working by adding: ``` hostNetwork: true securityContext: privileged: true ``` in https://github.com/digitalocean/csi-digitalocean/blob/release-1.3/deploy/kubernetes/releases/csi-digitalocean-v1.3.0.yaml#L142

@timoreimann Yes on the controller. @dustymabe mentioned that openshift has stricter security settings than base kubernetes.

@dustymabe Done!

#122