velero-fips
Velero-FIPS Overview
Secure your stack with a FIPS-validated, hardened Velero 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.
Velero (formerly Heptio Ark) is used for backing up, restoring, and migrating Kubernetes clusters and persistent volumes.
FIPS 140-3 Certification
This image is FIPS-validated to ensure its cryptographic operations meet the Federal Information Processing Standards (FIPS) required for secure government and regulated environments. Its core cryptographic modules are validated under the NIST Cryptographic Module Validation Program (CMVP) and comply with the FIPS 140-3 standard.
To verify that the FIPS 140-3 provider is configured and active, follow the instructions in the FIPS compliance tab.
Try It Out
For a quick test, print the help menu:
docker run --rm \
reg.mini.dev/velero-fips --helpDeploy in Kubernetes with a Helm chart
Prerequisites
- A running Kubernetes cluster (v1.21 or higher is recommended)
- Helm v3.8 or higher for OCI support (Installation instructions)
kubectlinstalled and configured
Step 1: Start Cluster
If you have a cluster to work with, skip this step. Otherwise, start a Minikube cluster. Deployment instructions
Step 2: Add Repository to your Local Client
Add the Helm chart to your local Helm client.
helm repo add vmware-tanzu https://vmware-tanzu.github.io/helm-charts
helm repo updateStep 3: Deploy via Helm Chart
To deploy the chart with the Minimus image on a test namespace, add your provider configurations to the following command:
helm install velero vmware-tanzu/velero \
--namespace velero-ns \
--create-namespace \
--set image.repository=reg.mini.dev/velero-fips \
--set image.tag=latestFor example, to deploy in AWS with MinIO:
helm install velero vmware-tanzu/velero \
--namespace velero-ns \
--create-namespace \
--set image.repository=reg.mini.dev/velero-fips \
--set image.tag=latest \
--include-crds \
--set initContainers[0].name=velero-plugin-for-aws \
--set initContainers[0].image="velero/velero-plugin-for-aws:{AWS_PLUGIN_TAG} \
--set initContainers[0].imagePullPolicy=IfNotPresent \
--set initContainers[0].volumeMounts[0].mountPath=/target \
--set initContainers[0].volumeMounts[0].name=plugins \
--set configuration.backupStorageLocation[0].name=default \
--set configuration.backupStorageLocation[0].provider=aws \
--set configuration.backupStorageLocation[0].bucket={BUCKET_NAME} \
--set configuration.backupStorageLocation[0].default=true \
--set configuration.backupStorageLocation[0].config.region=minio \
--set configuration.backupStorageLocation[0].config.s3ForcePathStyle=true \
--set configuration.backupStorageLocation[0].config.s3Url=http://minio.minio.svc.cluster.local:9000 \
--set configuration.volumeSnapshotLocation[0].name=default \
--set configuration.volumeSnapshotLocation[0].provider=aws \
--set configuration.volumeSnapshotLocation[0].config.region=minio \
--set-file credentials.secretContents.cloud={DIR/to/credentials/for/velero} \
--set credentials.useSecret=true \
--set upgradeCRDs=false \
--set deployNodeAgent=false Wait a minute and check that the Pods are up and running:
kubectl -n velero-ns get poVerify that the chart deployed the expected Minimus image:
kubectl -n velero-ns describe deploy velero | grep Image:Step 4: Clean Up
Uninstall the chart to delete the namespace and its resources, including Pods, Deployments, Services, Secrets, ConfigMaps, etc.:
helm uninstall velero -n velero-nsTechnical Considerations
The Velero-FIPS image provided by Minimus is a FIPS-validated, slim, security-hardened alternative to the public image. The images are largely interchangeable, with a few differences as noted below.
Velero-FIPS built by Minimus:
- Runs as non-root by default as user 1000. The public image runs as user 1001.
- 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.