velero-plugin-for-gcp-fips

Chainguard Container for velero-plugin-for-gcp-fips

FIPS-compliant Velero plugin for Google Cloud Platform that provides backup and restore functionality for GCS and GCE Persistent Disk snapshots

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/velero-plugin-for-gcp-fips:latest

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

Compatibility Notes

The velero-plugin-for-gcp-fips image is a FIPS-compliant version fully compatible with the public Velero plugin for GCP. This FIPS-compliant image includes both the VolumeSnapshotter and ObjectStore plugins required for Google Cloud integration:

• VolumeSnapshotter: Handles GCE Persistent Disk snapshots for persistent volume backups
• ObjectStore: Manages backups stored in Google Cloud Storage

The plugin is designed to be used as an init container with Velero deployments, following the standard Velero plugin architecture. This FIPS-compliant version uses validated cryptographic modules and algorithms that meet Federal Information Processing Standards requirements. There are no functional changes from the public implementation.

Getting Started

The velero-plugin-for-gcp-fips image is designed to be used as an init container in Velero deployments. The image contains a cp-plugin command that copies the plugin binary to a shared volume where Velero can load it.

Here's an example of using this image with a Velero deployment:

apiVersion: apps/v1
kind: Deployment
metadata:
  name: velero
  namespace: velero
spec:
  template:
    spec:
      serviceAccountName: velero
      initContainers:
      - name: velero-plugin-for-gcp-fips
        image: cgr.dev/ORGANIZATION/velero-plugin-for-gcp-fips:latest
        volumeMounts:
        - mountPath: /target
          name: plugins
      containers:
      - name: velero
        image: cgr.dev/ORGANIZATION/velero:latest
        command:
        - /velero
        args:
        - server
        - --plugin-dir=/plugins
        volumeMounts:
        - name: plugins
          mountPath: /plugins
      volumes:
      - name: plugins
        emptyDir: {}

When the init container runs, it will copy the plugin binary to /target/velero-plugin-for-gcp, making it available to the Velero server in the /plugins directory.

You can also install Velero with this plugin using the official Velero CLI:

velero install \
  --provider gcp \
  --plugins cgr.dev/ORGANIZATION/velero-plugin-for-gcp-fips:latest \
  --bucket my-backup-bucket \
  --secret-file ./credentials-velero

Configuration

To use this plugin, you'll need to configure Velero with GCP-specific settings. Create a BackupStorageLocation resource:

apiVersion: velero.io/v1
kind: BackupStorageLocation
metadata:
  name: gcp
  namespace: velero
spec:
  provider: velero.io/gcp
  objectStorage:
    bucket: my-backup-bucket
    prefix: velero-backups
  config:
    project: my-gcp-project

For GCE Persistent Disk snapshots, create a VolumeSnapshotLocation:

apiVersion: velero.io/v1
kind: VolumeSnapshotLocation
metadata:
  name: gcp
  namespace: velero
spec:
  provider: velero.io/gcp
  config:
    project: my-gcp-project

You'll also need to provide GCP credentials to Velero. Create a secret with your GCP service account credentials:

kubectl create secret generic cloud-credentials \
  --namespace velero \
  --from-file cloud=path/to/gcp-service-account.json

Documentation and Resources

• Velero plugin for GCP documentation
• Velero supported providers documentation

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.