Skip to content

Commit eee9d83

Browse files
NickJosevskiclaude
andcommitted
Address review: CSI driver provider table, keep workload IAM link
Per Liam's review nits on PR #3246: - Replace the CSI driver prose with a per-provider table (EKS, AKS, GKE, OpenShift) linking directly to each provider's CSI driver setup docs, noting the RWO vs RWX driver options. - Keep the workload IAM role service-account annotation link in its own info block. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
1 parent 4b48334 commit eee9d83

1 file changed

Lines changed: 10 additions & 3 deletions

File tree

  • src/pages/docs/kubernetes/targets/kubernetes-agent

src/pages/docs/kubernetes/targets/kubernetes-agent/storage.md

Lines changed: 10 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -55,10 +55,17 @@ Many managed Kubernetes offerings will provide storage that require little effor
5555
See this [blog post](https://octopus.com/blog/efs-eks) for a tutorial on connecting EFS to and EKS cluster.
5656
:::
5757

58-
:::div{.info}
59-
Cloud provider CSI drivers (such as the [AWS EBS CSI driver](https://docs.aws.amazon.com/eks/latest/userguide/ebs-csi.html) or the EFS CSI driver) often need to be installed as an add-on and given an IAM role with a trust relationship (for example [IRSA](https://docs.aws.amazon.com/eks/latest/userguide/iam-roles-for-service-accounts.html) on EKS, or [Workload Identity](https://cloud.google.com/kubernetes-engine/docs/how-to/workload-identity) on GKE) before they can provision volumes. Follow the linked provider documentation to install the driver and configure these permissions, then reference the resulting `StorageClass` name when installing the agent.
58+
Cloud provider CSI drivers usually need to be installed as an add-on and given an IAM role with a trust relationship (for example [IRSA](https://docs.aws.amazon.com/eks/latest/userguide/iam-roles-for-service-accounts.html) on EKS, or [Workload Identity](https://cloud.google.com/kubernetes-engine/docs/how-to/workload-identity) on GKE) before they can provision volumes. Follow the provider documentation below to install the correct driver and configure these permissions, then reference the resulting `StorageClass` name when installing the agent.
59+
60+
| **Provider** | **CSI driver setup documentation** |
61+
| ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
62+
| Amazon EKS | [Amazon EBS CSI driver](https://docs.aws.amazon.com/eks/latest/userguide/ebs-csi.html) (RWO) · [Amazon EFS CSI driver](https://docs.aws.amazon.com/eks/latest/userguide/efs-csi.html) (RWX) |
63+
| Azure AKS | [Azure Disk CSI driver](https://learn.microsoft.com/en-us/azure/aks/azure-disk-csi) (RWO) · [Azure Files CSI driver](https://learn.microsoft.com/en-us/azure/aks/azure-files-csi) (RWX) |
64+
| Google GKE | [Compute Engine persistent disk CSI driver](https://cloud.google.com/kubernetes-engine/docs/how-to/persistent-volumes/gce-pd-csi-driver) (RWO) · [Filestore CSI driver](https://cloud.google.com/kubernetes-engine/docs/how-to/persistent-volumes/filestore-csi-driver) (RWX) |
65+
| Red Hat OpenShift | [Configuring CSI volumes](https://docs.openshift.com/container-platform/latest/storage/container_storage_interface/persistent-storage-csi.html) |
6066

61-
Separately, if your **deployment workloads** need to assume an IAM role, you can annotate the script pod service account — see [setting scriptPod service account annotations](/docs/kubernetes/targets/kubernetes-agent/troubleshooting#setting-scriptpod-service-account-annotations).
67+
:::div{.info}
68+
If your **deployment workloads** need to assume an IAM role, you can annotate the script pod service account — see [setting scriptPod service account annotations](/docs/kubernetes/targets/kubernetes-agent/troubleshooting#setting-scriptpod-service-account-annotations).
6269
:::
6370

6471
If you manage your own cluster and don’t have offerings from cloud providers available, there are some in-cluster options you could explore:

0 commit comments

Comments
 (0)