Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[K8S010] Migrate In-tree storage plugin to CSI driver #11

Open
bryantbiggs opened this issue Feb 7, 2023 · 1 comment
Open

[K8S010] Migrate In-tree storage plugin to CSI driver #11

bryantbiggs opened this issue Feb 7, 2023 · 1 comment
Labels
check feature-request Request for a new feature

Comments

@bryantbiggs
Copy link
Member

Use case

Starting in Kubernetes v1.17, the in-tree storage plugin was marked as deprecated and it will be removed in EKS v1.23. Users need to install to the EBS CSI driver prior to upgrading to EKS v1.23

The in-tree Amazon EBS storage provisioner is deprecated. If you are upgrading your cluster to version 1.23, then you must first install the Amazon EBS driver before updating your cluster. For more information, see Amazon EBS CSI migration frequently asked questions. If you have pods running on a version 1.22 or earlier cluster, then you must install the Amazon EBS driver before updating your cluster to version 1.23 to avoid service interruption. https://docs.aws.amazon.com/eks/latest/userguide/ebs-csi-migration-faq.html

Solution/User Experience

  • Report if the cluster does not have the EBS CSI driver installed
  • Report on the usage of kubernetes.io/aws-ebsStorageClass and recommend users update to the new API resource groups provided by the CSI

Alternative solutions

None
@bryantbiggs bryantbiggs added triage feature-request Request for a new feature check and removed triage labels Feb 7, 2023
@bryantbiggs
Copy link
Member Author

Need to find a definitive way of determining if the EBS CSI driver is installed. Straightforward if installed via EKS Addon, less so if users have installed as self-managed (i.e. - Helm chart)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
check feature-request Request for a new feature
Projects
Status: Todo
Development

No branches or pull requests

1 participant