Chainguard Container for crossplane-gcp-storage-fips

FIPS-compliant Crossplane GCP Providers deliver Kubernetes-native APIs for provisioning and managing Google Cloud resources through Crossplane.

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/crossplane-gcp-storage-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

Chainguard's FIPS compliant Crossplane GCP providers are comparable to upstream GCP providers with the following architectural differences:

• Upstream providers can be deployed independently and automatically resolve their dependencies
• Chainguard providers require manual installation of the family provider and use skipDependencyResolution: true for component providers to prevent automatic upstream dependency resolution
• Deployment pattern: Install the Chainguard family provider first, then add individual component providers as needed
• Functionality: Provides equivalent GCP resource management capabilities with this modified deployment approach

FIPS Compliance

These FIPS-compliant images include OpenSSL FIPS provider and are built with FIPS-validated cryptographic modules. Key FIPS features include:

• FIPS-validated OpenSSL provider - Uses OpenSSL FIPS provider for cryptographic operations
• Approved algorithms only - Restricted to FIPS-approved cryptographic algorithms
• FIPS mode enforcement - Cryptographic operations automatically use FIPS-validated modules
• Enhanced SSH security - SSH configurations restricted to FIPS-approved ciphers and algorithms

Getting Started

Using the GCP Family Provider

For comprehensive GCP resource management, install the family provider that includes all GCP services:

apiVersion: pkg.crossplane.io/v1
kind: Provider
metadata:
  name: provider-family-gcp
spec:
  package: cgr.dev/ORGANIZATION/crossplane-gcp-provider-family-fips:latest

Using Individual Component Providers

For targeted deployments, install specific component providers alongside the family provider. Use skipDependencyResolution: true to prevent default upstream family provider installation:

apiVersion: pkg.crossplane.io/v1
kind: Provider
metadata:
  name: provider-gcp-storage
spec:
  package: cgr.dev/ORGANIZATION/crossplane-gcp-storage-fips:latest
  skipDependencyResolution: true
---
apiVersion: pkg.crossplane.io/v1
kind: Provider
metadata:
  name: provider-gcp-gke
spec:
  package: cgr.dev/ORGANIZATION/crossplane-gcp-gke-fips:latest
  skipDependencyResolution: true

Configuration

After installing your desired providers, configure GCP credentials using a ProviderConfig:

# Create service account key secret
cat <<EOF | kubectl apply -f -
apiVersion: v1
kind: Secret
metadata:
  name: gcp-secret
  namespace: crossplane-system
type: Opaque
stringData:
  creds: |
    $(cat /path/to/service-account-key.json)
EOF

# Create ProviderConfig
cat <<EOF | kubectl apply -f -
apiVersion: gcp.m.upbound.io/v1beta1
kind: ClusterProviderConfig
metadata:
  name: default
spec:
  projectID: <your-project-id>
  credentials:
    source: Secret
    secretRef:
      namespace: crossplane-system
      name: gcp-secret
      key: creds
EOF

Once configured, you can create GCP resources. Example Cloud Storage bucket creation:

apiVersion: storage.gcp.m.upbound.io/v1beta1
kind: Bucket
metadata:
  name: my-secure-bucket
spec:
  forProvider:
    location: US-CENTRAL1
    project: your-project-id
  providerConfigRef:
    name: default

Available Images

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.