domains / families / devops / google-cloud-storage-fuse

google-cloud-storage-fuse

separate

Mounts Cloud Storage buckets on Google Cloud as a POSIX file system with Cloud Storage FUSE (gcsfuse). Use when interacting with gcsfuse or Cloud Storage FUSE mounts: decide whether FUSE, native gs:// reads, or Filestore/Managed Lustre fits a workload, deploy tuned mounts on GKE, Compute Engine, or Cloud Run, enable and size file, stat, and list caches, tune mount flags (--implicit-dirs) or config files, apply workload profiles, keep ML checkpointing safe (rename atomicity, hierarchical namespace/HNS, close-time finalization, concurrent writers), or diagnose slow training, low throughput, or bill spikes with gcsfuse metrics. Covers mount semantics, gcsfuse CLI and configs, GKE gcsfuse CSI driver (Workload Identity principal:// bindings, profile StorageClasses, sidecar sizing), and Cloud Run volume mounts. Don't use for bucket administration without a mount (google-cloud-storage-basics) or POSIX shared file systems (Filestore, Managed Lustre; use gke-storage).

When to use

• deciding whether to use FUSE, native gs:// reads, or Filestore/Managed Lustre
• deploying tuned mounts on GKE, Compute Engine, or Cloud Run
• enabling and sizing file, stat, and list caches
• tuning mount flags or config files
• applying workload profiles
• keeping ML checkpointing safe
• diagnosing slow training, low throughput, or bill spikes
• managing GKE gcsfuse CSI driver and Cloud Run volume mounts

When not to use

• bucket administration without a mount
• POSIX shared file systems like Filestore or Managed Lustre

Skill page

Source