#VMware on AWS - ONTAP

1 messages · Page 1 of 1 (latest)

tender steppe
#

Hi there, I'm currently utilizing VMware Cloud on AWS and managing Kubernetes clusters within it. My objective is to provision PVCs in the NFS style. Initially, I considered employing EFS, but unfortunately, it lacks compatibility. Consequently, I've become acquainted with Amazon FSx for NetApp ONTAP as a viable alternative. While perusing the documentation, it's evident that the provisioning process takes place through the AWS console. Following this setup, I'm interested in understanding the subsequent steps required for creating PVCs. Do I need to install any specific CSI drivers or helm charts related to this? Your insights would be greatly appreciated.

proud forge
#

@candid steppe you might be best to start the conversation at least.

lone breach
tender steppe
#

Thanks @proud forge / @lone breach for sharing these resources

proud forge
#

Yw

tender steppe
#

Hello , I Installed Trident and now trying to connect to a NetApp Fsx deployed on AWS . However I am seeing following errors

#

time="2023-08-16T13:10:56Z" level=info msg="deferred syncing TridentBackendConfig 'trident/backend-tbc-ontap-nas', requeuing; reconcile deferred; problem initializing storage driver 'ontap-nas': error validating ontap-nas driver: driver validation failed: data LIF validation failed: could not find Data LIF for 10.150.85.140" crdControllerEvent=add logLayer=crd_frontend logSource=trident-crd-controller requestID=10395918-a692-4219-b296-7fe9d1po87 requestSource=CRD workflow="cr=reconcile"
time="2023-08-16T13:11:35Z" level=warning msg="Could not determine controller serial numbers. API status: failed, Reason: Insufficient privileges: user 'fsxadmin' does not have read access to this resource, Code: 13003" crdControllerEvent=add logLayer=core requestID=e08e308f-6720-43d4-8e28-89798hsa requestSource=CRD workflow="cr=reconcile"