kubernetes-csi-attacher

Infra

docker pull reg.mini.dev/kubernetes-csi-attacher

Infra

Updated yesterday

docker pull reg.mini.dev/kubernetes-csi-attacher

Kubernetes-CSI-Attacher Overview

Secure your stack with a hardened Kubernetes-CSI-Attacher image freshly-built by Minimus. Minimus images always include the most up-to-date package version for all packages and dependencies contained in the image.

The Kubernetes CSI Attacher is an external sidecar container that watches Kubernetes VolumeAttachment objects and triggers ControllerPublish and ControllerUnpublish operations against a CSI endpoint. It is a required component of the CSI controller plugin for storage drivers that support dynamic volume attachment.

Try It Out

Prerequisites

A running Kubernetes cluster (v1.21 or higher is recommended)
A CSI driver deployed in your cluster that supports the ControllerPublish capability
kubectl installed and configured

Step 1: Deploy the CSI Attacher as a Sidecar

The CSI Attacher runs as a sidecar container alongside your CSI controller plugin. Create a StatefulSet with the Minimus csi-attacher image:

cat <<EOF | kubectl apply -f -
apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: csi-controller
  namespace: kube-system
spec:
  selector:
    matchLabels:
      app: csi-controller
  serviceName: csi-controller
  replicas: 1
  template:
    metadata:
      labels:
        app: csi-controller
    spec:
      serviceAccountName: csi-attacher
      containers:
        - name: csi-attacher
          image: reg.mini.dev/kubernetes-csi-attacher:latest
          args:
            - --v=5
            - --csi-address=/csi/csi.sock
            - --leader-election
          volumeMounts:
            - name: socket-dir
              mountPath: /csi
        - name: csi-driver
          image: your-csi-driver:latest
          volumeMounts:
            - name: socket-dir
              mountPath: /csi
      volumes:
        - name: socket-dir
          emptyDir: {}
EOF

Step 2: Verify the Attacher is Running

kubectl -n kube-system get pods -l app=csi-controller

Step 3: Clean Up

kubectl -n kube-system delete statefulset csi-controller

Technical Considerations

The Kubernetes-CSI-Attacher image provided by Minimus is a slim, security-hardened alternative to the public image. The images are largely interchangeable, with a few differences as noted below.

Kubernetes-CSI-Attacher built by Minimus:

Runs as non-root by default for a security-first approach that protects against privilege escalation attacks.
Drill down on the version specification tab to see the default user, listening ports, entrypoint, volumes, environment variables, etc.

The Payoff

A hardened, minimal image that will remain more secure for the long run and accrue vulnerabilities at a slower rate.

See the risk reduction dashboard for a detailed CVE comparison over the past 30 days.
Review the compliance report to see the default hardening and security configurations for the image.

Terms & Info

Trademark

This catalog is published by Minimus. All product names, logos, and marks, other than those belonging to Minimus, shown are owned by their respective rights holders and appear here only to identify the open source software each image contains. Minimus claims no ownership of those marks and implies no affiliation with, endorsement by, certification by, or sponsorship by any rights holder.

Disclaimer

Images are provided "as-is" without warranty of any kind. "Hardened" refers to the security configuration applied at the time of build and does not constitute a guarantee of ongoing security or absence of vulnerabilities. The free tier is provided without support, SLA, or guaranteed patching timelines. Security updates may be applied to paid subscriptions before or instead of free tier images. By pulling or using any image you agree to our Terms of Use.