aws-fsx-csi-driver

Chainguard Container for aws-fsx-csi-driver

Minimal container image for aws-fsx-csi-driver, the CSI driver for Amazon FSx for Lustre.

Chainguard Containers are regularly-updated, secure-by-default container images.

Download this Container Image

For those with access, this container image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/aws-fsx-csi-driver:latest

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.

Compatibility Notes

Chainguard's AWS FSx CSI driver image is a drop-in replacement for the upstream public.ecr.aws/fsx-csi-driver/aws-fsx-csi-driver image.

As with many Chainguard container images, this image contains only the minimum dependencies needed to function. It does not include a shell or package manager.

Getting Started

The FSx CSI driver enables Kubernetes pods to access Amazon FSx for Lustre file systems. It consists of two components:

• Controller: Handles volume provisioning and management (runs as a Deployment)
• Node: Handles volume mounting on nodes (runs as a DaemonSet)

Prerequisites

Before installing the FSx CSI driver, ensure you have:

• An Amazon EKS cluster or self-managed Kubernetes cluster on AWS
• IAM permissions for the driver to interact with FSx service
• A VPC configuration that allows FSx access

Refer to the AWS documentation on creating an IAM role for detailed setup instructions.

Install with Helm

The recommended installation method is using the official Helm chart.

First, create a values.yaml file to configure the Helm chart with the Chainguard image:

image:
  repository: cgr.dev/ORGANIZATION/aws-fsx-csi-driver
  tag: latest

controller:
  serviceAccount:
    create: true
    name: fsx-csi-controller-sa
    annotations:
      eks.amazonaws.com/role-arn: arn:aws:iam::ACCOUNT_ID:role/FSxCSIDriverRole

node:
  serviceAccount:
    create: true
    name: fsx-csi-node-sa

Replace ORGANIZATION with your Chainguard organization name and ACCOUNT_ID with your AWS account ID.

Add the Helm repository and install:

helm repo add aws-fsx-csi-driver https://kubernetes-sigs.github.io/aws-fsx-csi-driver/
helm repo update

helm upgrade --install aws-fsx-csi-driver \
  --namespace kube-system \
  aws-fsx-csi-driver/aws-fsx-csi-driver \
  -f values.yaml

Verify Installation

After installation, verify the driver is running:

# Check controller deployment
kubectl get deployment -n kube-system fsx-csi-controller

# Check node daemonset
kubectl get daemonset -n kube-system fsx-csi-node

# Verify CSI driver registration
kubectl get csidrivers fsx.csi.aws.com

Documentation and Resources

• AWS FSx CSI Driver GitHub Repository
• Amazon FSx for Lustre Documentation
• EKS FSx CSI Driver Setup Guide
• FSx CSI Driver Helm Chart
• Dynamic Provisioning Examples
• Static Provisioning Examples

What are Chainguard Containers?

Chainguard's free tier of Starter container images are built with Wolfi, our minimal Linux undistro.

All other Chainguard Containers are built with Chainguard OS, Chainguard's minimal Linux operating system designed to produce container images that meet the requirements of a more secure software supply chain.

The main features of Chainguard Containers include:

• Minimal design, without unnecessary software bloat
• Daily builds to ensure container images are up-to-date with available security patches
• High quality build-time SBOMs attesting to the provenance of all artifacts within the image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a development, or -dev, variant.

In all other cases, including Chainguard Containers tagged as :latest or with a specific version number, the container images include only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager.

Although the -dev container image variants have similar security features as their more minimal versions, they include additional software that is typically not necessary in production environments. We recommend using multi-stage builds to copy artifacts from the -dev variant into a more minimal production image.

Need additional packages?

To improve security, Chainguard Containers include only essential dependencies. Need more packages? Chainguard customers can use Custom Assembly to add packages, either through the Console, chainctl, or API.

To use Custom Assembly in the Chainguard Console: navigate to the image you'd like to customize in your Organization's list of images, and click on the Customize image button at the top of the page.

Learn More

Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.

Trademarks

This software listing is packaged by Chainguard. The trademarks set forth in this offering are owned by their respective companies, and use of them does not imply any affiliation, sponsorship, or endorsement by such companies.