[docs] Bootstrapping EKS cluster requires additional CSI driver configuration

Bug #2016882 reported by Bartlomiej Gmerek
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Triaged
High
Teodora Mihoc

Bug Description

Hi,

Starting from K8s 1.23, there are additional steps needed to bootstrap a Juju controller on an EKS cluster. Without creating an EBS CSI driver service account, bootstrapping controller will timeout waiting for the volumes. This information is missing from the official docs.

Required steps are:

eksctl utils associate-iam-oidc-provider --region=<REGION> --cluster=<EKS CLUSTER NAME> --approve

eksctl create iamserviceaccount --name ebs-csi-controller-sa --namespace kube-system --cluster <EKS CLUSTER NAME> --attach-policy-arn arn:aws:iam::aws:policy/service-role/AmazonEBSCSIDriverPolicy --approve --role-only --role-name AmazonEKS_EBS_CSI_DriverRole

eksctl create addon --name aws-ebs-csi-driver --cluster <EKS CLUSTER NAME> --service-account-role-arn <SERVICE ACCOUNT ARN> --force

Kindly please update the docs.

Thanks in advance.

BR,
Bartek

Harry Pidcock (hpidcock)
Changed in juju:
importance: Undecided → High
status: New → Triaged
assignee: nobody → Teodora Mihoc (tmihoc)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.