Unable to attach or mount volumes

[jailbreakerSN]

Hello,

I'm facing a issu when trying to test csi-gcs on GKE after creating the secret csi-gcs-secret

• kubectl create secret generic csi-gcs-secret --from-literal=bucket=<BUCKET_NAME> --from-file=key=<PATH_TO_SERVICE_ACCOUNT_KEY>
• kubectl apply -k "github.com/ofek/csi-gcs/examples/static?ref=v0.7.0" The errors I got are:
• AttachVolume.Attach failed for volume "csi-gcs-pv" : attachdetachment timeout for volume csi-gcs
• Unable to attach or mount volumes: unmounted volumes=[csi-gcs-pvc], unattached volumes=[csi-gcs-pvc default-token-n6w8k]: timed out waiting for the condition

[jailbreakerSN]

@ofek can you check please my issue? Thanks in advance!

[ofek]

@dysosmus Do you think this might be related to https://github.com/ofek/csi-gcs/pull/72?

[dysosmus]

@ofek I can observe similar events in our clusters and it's related to the driver starting up. In our case, those warnings are however transitory and doesn't prevent the pod from eventually start.

[jailbreakerSN]

Or course @dysosmus, it doesn't prevent the pod from start, but stay at containairizing step, because it seems to wait for a volume that never provided !

[dysosmus]

it doesn't prevent the pod from start, but stay at containairizing step, because it seems to wait for a volume that never provided !

@ofek Then that seem different, from what I'm working on #72 :( . In my experience, the container eventually start after ±1-2 minutes of retries.

@jailbreakerSN is the csi-gcs driver pod is running properly on the node where your pod is running?

[jailbreakerSN]

Hello @dysosmus , Yes, I think all is running (same namespace, same node) like the commands I specified earlier. I put the Key and bucket Bâle correctly and ran out with kubectl

[ofek]

@maennchen Do you have any ideas?

[jailbreakerSN]

@ofek @dysosmus , might it be related to the status of my cluster, which is a private cluster?

[dysosmus]

@jailbreakerSN could be, do your subnet where your GKE cluster nodes are running have Google Private Access enabled? You can also try to spin up a GCP Cloud NAT on the subnet, but afaik that shouldn't be needed if Private Access is enabled.

[maennchen]

@jailbreakerSN Can you capture the log of the csi-gcs DaemonSet pods while you provision a new PVC and start a pod using it?

[elamcheliyan]

@jailbreakerSN , Is this issue still present? even I want to try this in my GKE services