Chainguard Image for aws-volume-modifier-for-k8s

Chainguard Images are regularly-updated, minimal container images with low-to-zero CVEs.

Download this Image

This image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/aws-volume-modifier-for-k8s:latest

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

Installation

For the documentation about the EBS CSI driver, please refer to the upstream documentation.

Install via helm

For full instruction, refer to the helm chart documentation.

Install the EBS CSI driver via the official Helm chart, enabling the volume-modify feature that enable the sidecar controller into the CSI driver controller Deployment, via the Helm value controller.volumeModificationFeature.enable.

Set the volumemodifier sidecar controller image to the Chainguard one, via the Helm values sidecars.volumemodifier.image.repository and sidecars.volumemodifier.image.tag.

Please find an example of values below:

sidecars:
  volumemodifier:
    image:
      repository: cgr.dev/chainguard/aws-volume-modifier-for-k8s
      tag: latest
controller:
  volumeModificationFeature:
    enabled: true

Below is an example, of how to use the helm chart, using both the EBS CSI driver and Volume Modifier Chainguard images.

Add the helm repo:

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

Install the chart:

helm upgrade --install aws-ebs-csi-driver --namespace kube-system aws-ebs-csi-driver/aws-ebs-csi-driver \
  --set controller.volumeModificationFeature.enabled=true \
  --set sidecars.volumemodifier.image.repository=cgr.dev/chainguard/aws-volume-modifier-for-k8s \
  --set sidecars.volumemodifier.image.tag=latest \
  --set image.repository=cgr.dev/chainguard-private/aws-ebs-csi-driver \
  --set image.tag=latest

Installation via EKS add-on

EKS supports installation of the ebs-csi-driver as an EKS add-on. There are instructions in the upstream documentation.

If you've chosen this installation method, keep in mind that you cannot specify a custom image whilst installing via EKS add-on.

You'll need to patch the ebs-csi-controller deployment to use the Chainguard image, however this is a step you'll need to repeat each time that you re-deploy or upgrade the version via EKS add-ons.

Volume modification

To modify volumes with annotations as expected by the volumemodifier EBS CSI driver's sidecar controller, please refer to the official documentation.

Supported annotations on PersistentVolumeClaims are:

• ebs.csi.aws.com/volumeType
• ebs.csi.aws.com/iops

For instance, you can set and update dynamically those attributes on a PersistentVolumeClaim like below:

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: ebs-claim
  annotations:
    ebs.csi.aws.com/volumeType: "io2"
    ebs.csi.aws.com/iops: "4000"
spec:
  accessModes:
    - ReadWriteOnce
  storageClassName: ebs-sc
  resources:
    requests:
      storage: 100Gi

Contact Support

If you have a Zendesk account (typically set up for you by your Customer Success Manager) you can reach out to Chainguard's Customer Success team through our Zendesk portal.

What are Chainguard Images?

Chainguard Images are a collection of container images designed for security and minimalism.

Many Chainguard Images are distroless; they contain only an open-source application and its runtime dependencies. These images do not even contain a shell or package manager. Chainguard Images are built with Wolfi, our Linux undistro designed to produce container images that meet the requirements of a secure software supply chain.

The main features of Chainguard Images include:

• Minimal design, with no unnecessary software bloat
• Automated nightly builds to ensure Images are completely up-to-date and contain all available security patches
• High quality build-time SBOMs (software bills of materials) attesting the provenance of all artifacts within the Image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

-dev Variants

As mentioned previously, Chainguard’s distroless Images have no shell or package manager by default. This is great for security, but sometimes you need these things, especially in builder images. For those cases, most (but not all) Chainguard Images come paired with a -dev variant which does include a shell and package manager.

Although the -dev image variants have similar security features as their distroless versions, such as complete SBOMs and signatures, they feature additional software that is typically not necessary in production environments. The general recommendation is to use the -dev variants only to build the application and then copy all application artifacts into a distroless image, which will result in a final container image that has a minimal attack surface and won’t allow package installations or logins.

That being said, it’s worth noting that -dev variants of Chainguard Images are completely fine to run in production environments. After all, the -dev variants are still more secure than many popular container images based on fully-featured operating systems such as Debian and Ubuntu since they carry less software, follow a more frequent patch cadence, and offer attestations for what they include.

Learn More

To better understand how to work with Chainguard Images, we encourage you to visit Chainguard Academy, our documentation and education platform.