crossplane-fips

Fips

Infra

Stig

Updated 4 days ago

Crossplane-FIPS Overview

Secure your stack with a hardened Crossplane-FIPS 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.

Crossplane is a Cloud Native Control Plane, a Kubernetes-native framework for building cloud infrastructure APIs. It extends Kubernetes with custom resources that let you provision and manage cloud services (AWS, GCP, Azure, and more) using standard Kubernetes tooling.

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

Prerequisites

A running Kubernetes cluster (v1.21 or higher is recommended)
Helm v3.8 or higher for OCI support (Installation instructions)
kubectl installed 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 Crossplane Helm chart to your local Helm client.

helm repo add crossplane-stable https://charts.crossplane.io/stable
helm repo update

Step 3: Deploy via Helm Chart

If you don't already have a namespace crossplane-system, create it:

kubectl create namespace crossplane-system

Pre-create the service accounts with the required Helm ownership metadata so they are in place before the chart deploys the pods:

for SA in crossplane rbac-manager; do
  kubectl create serviceaccount $SA -n crossplane-system
  kubectl annotate serviceaccount $SA -n crossplane-system \
    meta.helm.sh/release-name=crossplane \
    meta.helm.sh/release-namespace=crossplane-system
  kubectl label serviceaccount $SA -n crossplane-system \
    app.kubernetes.io/managed-by=Helm
done

Deploy Crossplane-FIPS:

helm upgrade --install crossplane crossplane-stable/crossplane \
  --namespace crossplane-system \
  --set image.repository='reg.mini.dev/crossplane-fips' \
  --set image.tag='latest'

Wait a minute and check that the Pods are up and running:

kubectl -n crossplane-system get po

Confirm that Minimus images were deployed:

kubectl -n crossplane-system describe pods | 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 crossplane -n crossplane-system

Technical Considerations

The Crossplane-FIPS image provided by Minimus is a slim, security-hardened alternative to the public image from Docker Hub. The images are largely interchangeable, with a few differences as noted below.

Crossplane-FIPS 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.