From d9c720a04d3dabc9e2b4719f16d6f10e91e18a15 Mon Sep 17 00:00:00 2001 From: davegallant Date: Mon, 8 Apr 2024 12:58:00 +0000 Subject: [PATCH] deploy: a2d6ebac0723f4cc5204161f8fb9230233561d76 --- blog/amazon-ebs-csi-driver-terraform/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blog/amazon-ebs-csi-driver-terraform/index.html b/blog/amazon-ebs-csi-driver-terraform/index.html index 32412a42..4b3bfb76 100644 --- a/blog/amazon-ebs-csi-driver-terraform/index.html +++ b/blog/amazon-ebs-csi-driver-terraform/index.html @@ -68,4 +68,4 @@ policy_arn = "arn:aws:iam::aws:policy/service-role/AmazonEBSCSIDriverPolicy" role = aws_iam_role.ebs_csi_driver.name } -

The above configuration follows the docs, binding an IAM role to the service account kube-system/ebs-csi-controller-sa using an OpenID connect provider.

After applying the changes above, I deployed the sample application and noticed that the persistent volume claims were bound to EBS volumes.



\ No newline at end of file +

The above configuration follows the docs, binding an IAM role to the service account kube-system/ebs-csi-controller-sa using an OpenID connect provider.

After applying the changes above, I deployed the sample application and noticed that the persistent volume claims were bound to EBS volumes.



\ No newline at end of file