[Feature] Enhance the user experience for creating an EKS cluster intended for stateful workloads.

[cshiv]

What feature/behavior/change do you want?

Creating an EKS cluster is simplified with the eksctl tool. However, if you run stateful workloads on a cluster created with eksctl's default configurations, it fails because the aws-ebs-csi-driver is missing, leading to PVC creation issues.

To address this problem, users need to use a config file with an add-on section when using eksctl:

addons:
- name: aws-ebs-csi-driver

It's worth noting that aws-ebs-csi-driver is not a default add-on to the EKS cluster. The reason for not including it as a default add-on is not specified.

The documentation currently lacks information on EBS CSI drivers, and users often discover the issue only after encountering it, especially new users. Since stateful workloads are increasingly common, it would be beneficial to document this information properly. Additionally, providing instructions in the documentation for installing add-ons using commands like:

eksctl create addon --name aws-ebs-csi-driver --cluster <cluster-name>

could be helpful.

Why do you want this feature?

Better user experience for the community which runs a stateful workload on EKS

[TiberiuGC]

Additionally, providing instructions in the documentation for installing add-ons using commands like:

eksctl create addon --name aws-ebs-csi-driver --cluster <cluster-name>
could be helpful.

Hi @cshiv - general information on how to manipulate EKS add-ons using eksctl can be found here.

It's worth noting that aws-ebs-csi-driver is not a default add-on to the EKS cluster. The reason for not including it as a default add-on is not specified.

Only universally required add-ons are default on EKS clusters (kube-proxy, VPC CNI, CoreDNS). While AWS EBS is a popular storage option for stateful workloads, other solutions exist. The choice belongs to the user.

The documentation currently lacks information on EBS CSI drivers, and users often discover the issue only after encountering it, especially new users.

eksctl docs do not go in-depth on how each EKS add-on works or what functionality it provides. Admittedly, the eksctl docs can refer to official AWS docs on that matter. Otherwise, what other explicit steps do you consider we should take in order to improve UX?

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[github-actions]

This issue was closed because it has been stalled for 5 days with no activity.