You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
'Failed to check and update snapshot content: failed to list snapshot for content restored-snapshot-content: "can not find snapshot for snapshotID projects/PROJECT_ID/global/snapshots/SNAPSHOT_ID"'
My first guess was that the CSI driver did not have the right IAM permissions to list or get the snapshots.
I am assuming that the CSI driver is not able to import snapshots from another project because of the way it was implemented.
If this was not the case and the CSI driver is supposed (and has been observed) to work cross-projects then any clue would be helpful to understand why it is failing to locate the snapshot in my case (is it because of IAM? did I misconfigure something? is my CSI driver version too old?).
Thank you!
The text was updated successfully, but these errors were encountered:
This issue is related to the topic discussed here: #224.
According to the documentation, it should be possible to import pre-existing snapshots across projects: https://github.com/kubernetes-sigs/gcp-compute-persistent-disk-csi-driver/blob/master/docs/kubernetes/user-guides/snapshots.md
But this doesn't seem to be the case:
My first guess was that the CSI driver did not have the right IAM permissions to
list
orget
the snapshots.I attempted to grant the following permissions:
to the following service accounts:
where
is an identity workload with service account
with no success.
I am assuming that the CSI driver is not able to import snapshots from another project because of the way it was implemented.
If this was not the case and the CSI driver is supposed (and has been observed) to work cross-projects then any clue would be helpful to understand why it is failing to locate the snapshot in my case (is it because of IAM? did I misconfigure something? is my CSI driver version too old?).
Thank you!
The text was updated successfully, but these errors were encountered: