Hi everyone,
We're trying to get Astra Trident to work with an EKS Anywhere deployment using Bottlerocket for the workload node OS. The nfs-utils package is not included in Bottlerocket. Does this mean we can't use Trident?
Thanks,
Josh
#EKS Anywhere Bottlerocket with Astra Trident
split rock
candid vale
Trident cannot test every platform available, but here are the docs, and some searches that may help:
(not specific to bottlerocket)
Trident docs:
-
Supported Frontends:
https://docs.netapp.com/us-en/trident/trident-get-started/requirements.html#supported-frontends-orchestrators -
Follow the steps here to install nfs-utils or nfs-common for EKS
https://docs.netapp.com/us-en/trident/trident-use/worker-node-prep.html#selecting-the-right-tools -
Astra blog re Trident install on AWS Anywhere
https://bluexp.netapp.com/blog/astra-blg-netapp-astra-supports-kubernetes-workloads-eks-anywhere
Astra blog for Trid
- EKS Bottlerocket github issue from 2020, offers some background and is closed issue:
https://github.com/bottlerocket-os/bottlerocket/issues/1225
If not working, check with EKS for more specific on NFS utils/common for bottlerocket. (Other folks from Astra team may have more info they can provide here....) Hope this is helpful!
split rock
Thanks for the information @candid vale . I can confirm that we are using a supported frontend (Kubernetes 1.25) and backend (ONTAP NFS). The Astra blog entry uses Ubuntu instead of Bottlerocket. We've considered switching to Ubuntu, but we'd rather not rearchitect our solution if possible.
Other CSI drivers such as aws-efs-csi-driver and csi-driver-nfs implement the nfs client in containers and don't use the client from the underlying OS.
Bottlrocket boots with a read only filesystem. We could build our own images as described at https://github.com/bottlerocket-os/bottlerocket/blob/develop/BUILDING.md, but that's a big pain compared to using off the shelf images.
split rock
Are there plans to move to using the NFS Go library in the CSI driver like others are doing?