You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: