Chainguard Container for aws-volume-modifier-for-k8s

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-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

What are Chainguard Containers?

Chainguard Containers are minimal container images that are secure by default.

In many cases, the Chainguard Containers tagged as :latest contain only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager. Chainguard Containers are built with Wolfi, our Linux undistro 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 -dev variant.

Although the -dev container image variants have similar security features as their more minimal versions, they feature additional software that is typically not necessary in production environments. We recommend using multi-stage builds to leverage the -dev variants, copying application artifacts into a final minimal container that offers a reduced attack surface that won’t allow package installations or logins.

Learn More

To better understand how to work with Chainguard Containers, please visit Chainguard Academy and Chainguard Courses.

In addition to Containers, Chainguard offers VMs and Libraries. Contact Chainguard to access additional products.

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.