CSI 드라이버를 설치한 후에는 Kubernetes StorageClass를 만들어야 합니다.
CSI 드라이버를 StorageClass의 프로비저닝 도구로 설정합니다. 그런 다음 StorageClass를 기본값으로 설정하거나 StorageClass를 사용하도록 워크로드를 구성할 수 있습니다.
CSI 드라이버 문서에서 프로비저닝 도구 이름을 포함하여 StorageClass에 제공하는 드라이버 관련 매개변수를 확인합니다.
특정 드라이버 또는 어플라이언스 이름 뒤가 아닌 속성(예: fast 또는 highly-replicated) 뒤에 StorageClass의 이름을 지정해야 합니다. 속성 뒤에 StorageClass 이름을 지정하면 서로 다른 클러스터와 환경에서 같은 이름으로 StorageClass를 만들 수 있습니다. 그런 다음 동일한 StorageClass를 사용하도록 워크로드를 구성합니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-07-29(UTC)"],[],[],null,["# Install additional CSI drivers\n\nThis page explains how to install a Container Storage Interface (CSI) storage\ndriver on your GKE clusters.\n\n[CSI](https://github.com/container-storage-interface/spec/blob/master/spec.md)\nis an open standard API that enables Kubernetes to expose arbitrary storage\nsystems to containerized workloads. Also, CSI enables the use of modern\nstorage features, such as and resizing and snapshots.\nBy default, GKE on AWS provisions [EBS volumes](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-volume-types.html) with the [`ebs-csi-driver`](https://github.com/kubernetes-sigs/aws-ebs-csi-driver). You can also provision [EFS volumes](/kubernetes-engine/multi-cloud/docs/aws/how-to/use-efs) with the [`efs-csi-driver`](https://github.com/kubernetes-sigs/aws-efs-csi-driver). If you want to use another type of storage volume, you can install a CSI driver.\n\n\u003cbr /\u003e\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/how-to/storage-class#set_default),\nor configure your workloads to use the StorageClass.\n\nBefore you begin\n----------------\n\n[Connect and authenticate to your cluster](/kubernetes-engine/multi-cloud/docs/aws/how-to/connect-and-authenticate-to-your-cluster)\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\nGoogle does not provide support or instructions for third-party drivers.\nContact 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\nUse a CSI driver\n----------------\n\nTo use a CSI driver, do the following:\n\n1. Create a custom [StorageClass](/kubernetes-engine/multi-cloud/docs/aws/how-to/storage-class#custom)\n which references 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/how-to/storage-class#set_default).\n\nConsiderations for StorageClass backed by a CSI driver\n------------------------------------------------------\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/how-to/storage-class#custom) which references the CSI driver."]]