Produk yang dijelaskan dalam dokumentasi ini, Cluster Anthos di AWS (generasi sebelumnya), kini berada dalam mode pemeliharaan. Semua penginstalan baru harus menggunakan produk generasi saat ini, cluster Anthos di AWS.
Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Topik ini menjelaskan cara menginstal driver penyimpanan Container Storage Interface (CSI) di cluster Anda.
Ringkasan
Secara default, GKE di AWS menyediakan volume EBS AWS menggunakan StorageClass default.
Jika workload Anda perlu menggunakan jenis volume penyimpanan lain, Anda dapat menginstal driver CSI yang kompatibel untuk menyediakan akses ke volume tersebut.
Container Storage Interface (CSI)
adalah API standar terbuka yang memberi workload Kubernetes akses ke sistem penyimpanan yang kompatibel. CSI juga memungkinkan penggunaan fitur penyimpanan modern seperti pengubahan ukuran dan snapshot.
Pertimbangan untuk StorageClass yang didukung oleh driver CSI
Saat Anda membuat StorageClass, pertimbangkan hal berikut:
Periksa dokumentasi driver CSI Anda untuk mengetahui parameter khusus driver yang Anda berikan ke StorageClass, termasuk nama penyedia.
Anda harus memberi nama StorageClass setelah propertinya (seperti fast atau
highly-replicated), bukan setelah nama driver atau alat tertentu di belakangnya. Saat memberi nama StorageClass setelah propertinya, Anda dapat membuat StorageClass dengan nama yang sama di cluster dan lingkungan yang berbeda. Kemudian, konfigurasi workload Anda untuk menggunakan StorageClass yang sama.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-07-22 UTC."],[],[],null,["# Install storage drivers\n\nThis topic explains how to install a Container Storage Interface (CSI) storage\ndriver on your clusters.\n\nOverview\n--------\n\nBy default, GKE on AWS provisions AWS\n[EBS volumes](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-volume-types.html)\nusing the default [StorageClass](/kubernetes-engine/multi-cloud/docs/aws/previous-generation/concepts/storage).\nIf your workloads need use another type of storage volume, you can install a\ncompatible CSI driver to provide access to it.\n\nThe `Container Storage Interface` ([CSI](https://github.com/container-storage-interface/spec/blob/master/spec.md))\nis an open standard API that gives Kubernetes workloads access to compliant\nstorage systems. CSI also enables the use of modern storage features such as\nresizing and snapshots.\n\nAfter installing a CSI driver, you need to create a Kubernetes\n[StorageClass](https://kubernetes.io/docs/concepts/storage/storage-classes/).\nYou set the CSI driver as the provisioner for the StorageClass. Then you can\n[set the StorageClass as default](/kubernetes-engine/multi-cloud/docs/aws/previous-generation/how-to/storage-class#set_default),\nor configure your workloads to use the StorageClass.\nFor an example of how to create a StatefulSet with a custom StorageClass,\nsee [Using StorageClasses with your workloads](/kubernetes-engine/multi-cloud/docs/aws/previous-generation/how-to/storage-class#example_statefulset).\n\nInstall a vendor's CSI driver\n-----------------------------\n\nStorage vendors are responsible for providing installation instructions for\ntheir CSI drivers. See the list of\n[CSI drivers](https://kubernetes-csi.github.io/docs/drivers.html)\nin the CSI documentation.\n\nFollow the installation instructions for your CSI driver, and then continue with\nthe next steps on this page.\n| **Important:** Google does not provide support or instructions for third-party drivers. Contact your storage vendor for support.\n\nVerify your driver installation\n-------------------------------\n\nAfter you install a CSI driver, you can verify the installation by running\nthe following commands. \n\n kubectl get csinodes \\\n -o jsonpath='{range .items[*]} {.metadata.name}{\": \"} {range .spec.drivers[*]} {.name}{\"\\n\"} {end}{end}'\n\nHow to use a CSI driver\n-----------------------\n\nTo use a CSI driver:\n\n1. Create a custom [StorageClass](/kubernetes-engine/multi-cloud/docs/aws/previous-generation/how-to/storage-class#custom)\n that refers to the driver in its `provisioner` field.\n\n2. To provision storage, you can either:\n\n - Reference the StorageClass in a [StatefulSet](https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/)'s `volumeClaimTemplates` specification.\n - [Set it as the cluster's default StorageClass](/kubernetes-engine/multi-cloud/docs/aws/previous-generation/how-to/storage-class#set_default).\n\n### Considerations for StorageClass backed by a CSI driver\n\nWhen you create a StorageClass, consider the following:\n\n- Check your CSI driver documentation for\n [driver-specific parameters](https://kubernetes.io/docs/concepts/storage/storage-classes/#the-storageclass-resource)\n that you provide to your StorageClass, including the provisioner name.\n\n- You should name the StorageClass after its properties (such as `fast` or\n `highly-replicated`), rather than after the name of the specific driver or\n appliance behind it. When you name a StorageClass after its properties, you can\n create StorageClasses with the same name in different clusters and\n environments. Then configure your workloads to use the same StorageClass.\n\nWhat's next\n-----------\n\n- Create a [StorageClass](/kubernetes-engine/multi-cloud/docs/aws/previous-generation/how-to/storage-class#custom) which references the CSI driver."]]
