velero-plugin-for-alicloud

packaged by Chainguard

Chainguard Container for velero-plugin-for-alicloud

Velero storage-provider plugin for Alibaba Cloud (OSS object store and ECS 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-alicloud:latest

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

Compatibility Notes

Chainguard's velero-plugin-for-alicloud builds the same velero-plugin-for-alibabacloud binary from the upstream v1.0.0 source and keeps the same /plugins → /target init-container contract, so Velero manifests that mount a shared /plugins volume between an init-container and the Velero container work unmodified.

The plugin registers three providers under velero.io/alibabacloud: an ObjectStore backed by Alibaba Cloud OSS, a VolumeSnapshotter backed by ECS disk snapshots, and a RestoreItemAction the controller uses during restore.

Two intentional differences from the upstream registry.cn-hangzhou.aliyuncs.com/acs/velero-plugin-alibabacloud image:

• User: this image runs as uid/gid 65532 (Chainguard nonroot) rather than nobody:nobody (uid 65534 on the upstream Debian base). The shared /target emptyDir needs to be writable by this uid; most charts set fsGroup: 65532 or leave the volume world-writable, both of which work.
• Entrypoint: upstream wraps the copy in /bin/bash -c "cp /plugins/* /target/.". This image's entrypoint is a direct cp /plugins/velero-plugin-for-alibabacloud /target/velero-plugin-for-alibabacloud invocation via busybox, which gives the same observable init-container result without a shell interpreter in the image.

Getting Started

Upstream v1.0.0 is installed with raw manifests (not the velero install CLI). Create the OSS credentials secret, then edit install/01-velero.yaml to use this image and apply it:

# 1. Set bucket + region
export BUCKET=<your-oss-bucket>
export REGION=<your-oss-region>

# 2. Create the velero namespace and the cloud-credentials secret
kubectl create namespace velero
kubectl create secret generic cloud-credentials -n velero \
    --from-file cloud=install/credentials-velero

# 3. Apply the CRDs and the Velero deployment, pointing the plugin
#    init-container at the Chainguard image:
kubectl apply -f install/00-crds.yaml
sed -i "s#<BUCKET>#$BUCKET#;s#<REGION>#$REGION#" install/01-velero.yaml
sed -i "s#registry.cn-hangzhou.aliyuncs.com/acs/velero-plugin-alibabacloud:[^ \"]*#cgr.dev/ORGANIZATION/velero-plugin-for-alicloud:latest#" install/01-velero.yaml
kubectl apply -f install/01-velero.yaml

See the upstream v1.0.0 install guide for the install/credentials-velero file format and the full OSS environment this plugin expects.

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.