Filestore-Unterstützung für Google Kubernetes Engine
Mit Sammlungen den Überblick behalten
Sie können Inhalte basierend auf Ihren Einstellungen speichern und kategorisieren.
Filestore-Instanzen sind vollständig verwaltete Dateiserver in Google Cloud, die Sie als dauerhaften Speicher mit ReadWriteMany-Zugriff für Ihre Google Kubernetes Engine (GKE)-Cluster verwenden können. Google Cloud
In diesem langlebigem oder nicht sitzungsspezifischem Speicher bleiben Ihre Daten über den Lebenszyklus Ihrer GKE-Pods hinaus bestehen.
Als dauerhafter Speicher mit ReadWriteMany-Zugriff können Ihre GKE PersistentVolumes als Volumes mit Lese-/Schreibzugriff von vielen Knoten bereitgestellt werden.
Im Gegensatz zum einzelnen Lese-/Schreibzugriffsmodus, der für Persistent Disk typisch ist, kann auf Filestore-Instanzen von mehreren GKE-Knoten gleichzeitig zugegriffen werden.
So können Sie Pods auf jedem verfügbaren GKE-Knoten starten und so die Effizienz Ihrer GKE-Cluster steigern.
Als eine Art Dateispeicher unterstützt Filestore mehrere nebenläufige Anwendungsinstanzen, die gleichzeitig auf dasselbe Dateisystem zugreifen.
[[["Leicht verständlich","easyToUnderstand","thumb-up"],["Mein Problem wurde gelöst","solvedMyProblem","thumb-up"],["Sonstiges","otherUp","thumb-up"]],[["Schwer verständlich","hardToUnderstand","thumb-down"],["Informationen oder Beispielcode falsch","incorrectInformationOrSampleCode","thumb-down"],["Benötigte Informationen/Beispiele nicht gefunden","missingTheInformationSamplesINeed","thumb-down"],["Problem mit der Übersetzung","translationIssue","thumb-down"],["Sonstiges","otherDown","thumb-down"]],["Zuletzt aktualisiert: 2025-08-18 (UTC)."],[[["\u003cp\u003eFilestore instances on Google Cloud offer fully managed, durable file storage with ReadWriteMany access for Google Kubernetes Engine (GKE) clusters, ensuring data persists beyond Pod lifecycles.\u003c/p\u003e\n"],["\u003cp\u003eUnlike Persistent Disk, Filestore allows multiple GKE nodes to simultaneously access the same instance, enabling Pods to be initiated on any available node for enhanced cluster efficiency.\u003c/p\u003e\n"],["\u003cp\u003eThe GKE Filestore CSI driver is the primary interface for utilizing Filestore with GKE, providing managed NFS storage via Kubernetes APIs and enabling dynamic provisioning of PersistentVolumes.\u003c/p\u003e\n"],["\u003cp\u003eFilestore multishares, combined with the GKE Filestore CSI driver, offer a unified view of PersistentVolumes, support dynamic scaling of storage capacity, and improve cost efficiency through smaller, more flexible share sizing.\u003c/p\u003e\n"]]],[],null,["# About Filestore support for Google Kubernetes Engine\n\nFilestore instances are fully managed file servers on Google Cloud that\nyou can use as durable storage with [ReadWriteMany](/kubernetes-engine/docs/concepts/persistent-volumes#access_modes)\naccess for your Google Kubernetes Engine (GKE) clusters.\n\n- As a type of durable or [non-ephemeral](/kubernetes-engine/docs/concepts/storage-overview)\n storage, your data persists beyond the lifecycle of your GKE\n Pods.\n\n- As durable storage with [ReadWriteMany](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#access-modes)\n access, your GKE [PersistentVolumes](/kubernetes-engine/docs/concepts/persistent-volumes#persistentvolumes)\n can be mounted as read-write by many nodes.\n\n- Unlike the single read-write access mode inherent to Persistent Disk, Filestore\n instances are accessible from multiple GKE nodes simultaneously.\n This lets you initiate Pods on any available GKE node, giving you greater\n efficiency of your GKE clusters.\n\n- As a type of [file storage](/filestore/docs/overview), Filestore\n supports multiple concurrent application instances accessing the same file\n system, simultaneously.\n\nFor more information, see [Deploy a stateful workload with Filestore](/kubernetes-engine/docs/tutorials/stateful-workload).\n\nFilestore and the GKE Filestore CSI driver\n------------------------------------------\n\nThe GKE Filestore CSI driver is the primary way for you\nto use Filestore instances with GKE and provides the\nfollowing benefits:\n\n- You have access to fully-managed NFS storage through the Kubernetes\n APIs ([`kubectl`](https://kubernetes.io/docs/tasks/administer-cluster/access-cluster-api)).\n\n- You can use the GKE Filestore CSI driver to dynamically\n provision your PersistentVolumes.\n\n- You can use the GKE Filestore CSI driver to create\n [CSI volume snapshots](/kubernetes-engine/docs/how-to/persistent-volumes/volume-snapshots)\n which subsequently create [Filestore backups](/filestore/docs/backups).\n\nFor a detailed list of benefits, see\n[Access instances with the GKE Filestore CSI driver](/filestore/docs/csi-driver).\n\nFilestore multishares for GKE\n-----------------------------\n\nFilestore multishares for GKE combined with the\n[GKE Filestore CSI driver](/kubernetes-engine/docs/how-to/persistent-volumes/filestore-csi-driver),\nversion 1.27 or later, provides the following benefits:\n\n- Provides a comprehensive view of your PersistentVolumes as one pool of storage.\n\n- Supports [dynamic volume provisioning](https://kubernetes.io/docs/concepts/storage/dynamic-provisioning/),\n scaling share and instance capacity up or down as needed.\n\n- Supports multiple shares with smaller, more flexible sizing for improved\n utilization and cost efficiency of each Filestore instance.\n\nFor more information, see [Filestore multishares for GKE](/filestore/docs/multishares).\n\nWhat's next\n-----------\n\n- [Deploy a stateful workload with Filestore](/kubernetes-engine/docs/tutorials/stateful-workload)\n- [StorageClasses and dynamic volume provisioning](/filestore/docs/multishares#storageclasses_and_dynamic_volume_provisioning)\n- [Access Filestore instances with the Filestore CSI driver](/kubernetes-engine/docs/how-to/persistent-volumes/filestore-csi-driver)\n- [Filestore multishares for GKE](/filestore/docs/multishares)\n- [Optimize storage with Filestore multishares for GKE](/kubernetes-engine/docs/tutorials/optimize-multishares)\n- [Encrypt your GKE clusters' persistent storage using CMEK](/kubernetes-engine/docs/how-to/using-cmek#create_a_cmek_protected_attached_disk)"]]
