GKE Cloud Storage FUSE Mount Failures and Dataplane V2 Connectivity Issues
Google Kubernetes Engine clusters using Cloud Storage FUSE may experience mount failures if the metadata service is not ready during sidecar initiation, impacting users on specific versions. A separate issue in GKE versions 1.35+ with Dataplane V2 can cause transient connectivity timeouts to the metadata server upon node startup. Mitigation involves upgrading GKE or implementing init containers, with further improvements planned for future patches.
Known issues (2) ›
- Google Kubernetes Engine
For GKE cluster version 1.34.1-gke.3899001 (sidecar mounter image version 1.21.9) and later affected versions, Cloud Storage FUSE volumes might fail to mount if the GKE metadata service isn't ready when the Cloud Storage FUSE sidecar initiates. When this issue occurs, you might see the following error: MountVolume.SetUp failed for volume "volume-name" : rpc error: code = Internal desc = the sidecar container terminated due to Error, exit code: 255 Additionally, the gcsfuse-sidecar container displays the following error: Failed to fetch identity pool and identity provider details required for b
- Google Kubernetes Engine
In GKE version 1.35 and later, due to faster node startup, workloads that use Dataplane V2 and Workload Identity Federation for GKE to authenticate to Google Cloud APIs might experience transient connectivity timeouts or refused connections to the GKE metadata server immediately following node startup. For recommendations and workarounds if this impacts your workload (for example, if your workload doesn't retry requests until they succeed), see Timeout errors at Pod startup , specifically by deploying an initContainer . Alternatively, add any that selects no workloads, such as in a namespace w
https://docs.cloud.google.com/release-notes#June_23_2026