aws-ebs-csi-driver-fips

Minimal images for aws-ebs-csi-driver.

Download this Image

The image is available on cgr.dev:

docker pull cgr.dev/chainguard/aws-ebs-csi-driver:latest

Testing

Since this application requires AWS credentials to be set up, we should create the required permissions before deploying it.

To do that, you can follow up on the official documentation here.

But for the sake of simplicity, we can create the Kubernetes secret resource called aws-secret with the proper options key_id and access_key:

kubectl create secret generic aws-secret \
    --namespace kube-system \
    --from-literal "key_id=${AWS_ACCESS_KEY_ID}" \
    --from-literal "access_key=${AWS_SECRET_ACCESS_KEY}"

There are several methods to deploy the driver, but we will use the helm method.

We should add the aws-ebs-csi-driver Helm repository to our repositories list:

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

Next, we can install the driver with the following command:

helm upgrade --install aws-ebs-csi-driver \
    --namespace kube-system \
    --set image.repository=cgr.dev/chainguard/aws-ebs-csi-driver \
    --set image.tag=latest \
    aws-ebs-csi-driver/aws-ebs-csi-driver

Once the driver has been deployed, verify the pods are running:

kubectl get pods -n kube-system -l app.kubernetes.io/name=aws-ebs-csi-driver