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

Remove CSI and storage class management from EKS-A for vSphere provider #5517

Closed
jiayiwang7 opened this issue Apr 3, 2023 · 2 comments · Fixed by #5659
Closed

Remove CSI and storage class management from EKS-A for vSphere provider #5517

jiayiwang7 opened this issue Apr 3, 2023 · 2 comments · Fixed by #5659
Assignees
Labels
Milestone

Comments

@jiayiwang7
Copy link
Member

jiayiwang7 commented Apr 3, 2023

Currently we have a specific storage class installed here https://github.com/aws/eks-anywhere/blob/main/pkg/providers/vsphere/config/defaultStorageClass.yaml which is not flexible, as well as unnecessary management of a driver that is not required for running a cluster. So we want to remove it from the EKS Anywhere create/upgrade flow so users can manage CSI on their own if they require it, with an implementation for VSphere listed here.

@drewvanstone
Copy link
Member

drewvanstone commented May 24, 2023

We will issue a warning that the CSI driver will be removed in an upcoming release. This issue is being moved to the 0.17 release

@vivek-koppuru
Copy link
Member

With #5918, we will give a warning to all our users when disableCSI is set to false or not specified to tell them to switch to managing their CSI driver and StorageClass on their own if they require it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants