Chainguard Container for spicedb-operator

SpiceDB Operator is a Kubernetes operator for managing SpiceDB clusters, providing automated deployment, scaling, and management of SpiceDB instances.

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/spicedb-operator: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 Chainguard spicedb-operator image is designed to be a drop-in replacement for the upstream authzed/spicedb-operator image.

Getting Started

Installing the SpiceDB Operator

To install the SpiceDB Operator on your Kubernetes cluster, first download the operator bundle:

curl -LO https://github.com/authzed/spicedb-operator/releases/latest/download/bundle.yaml

Then replace the operator image with the Chainguard image and apply:

sed -i 's|ghcr.io/authzed/spicedb-operator:.*|cgr.dev/ORGANIZATION/spicedb-operator:latest|g' bundle.yaml
kubectl apply --server-side -f bundle.yaml

Creating a SpiceDB Cluster with FIPS-Compliant Components

Once the operator is installed, you can create a SpiceDB cluster:

kubectl apply -f - <<EOF
apiVersion: v1
kind: Secret
metadata:
  name: spicedb-config
  namespace: default
stringData:
  preshared_key: "somerandomkeyatleastthirtytwocharacters"
  datastore_uri: "memory://"
---
apiVersion: authzed.com/v1alpha1
kind: SpiceDBCluster
metadata:
  name: spicedb
  namespace: default
spec:
  config:
    replicas: 1
    datastoreEngine: memory
    # Use FIPS-compliant SpiceDB image:
    image: "cgr.dev/ORGANIZATION/spicedb:latest"
  secretName: spicedb-config
EOF

For detailed configuration options, see the SpiceDB Operator documentation.

Documentation and Resources

• SpiceDB Operator Documentation
• SpiceDB Documentation
• SpiceDB on GitHub
• Authzed Community Discord

What are Chainguard Containers?

Chainguard Containers are minimal container images that are secure by default.

In many cases, the Chainguard Containers tagged as :latest contain only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager. Chainguard Containers are built with Wolfi, our Linux undistro 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 -dev variant.

Although the -dev container image variants have similar security features as their more minimal versions, they feature additional software that is typically not necessary in production environments. We recommend using multi-stage builds to leverage the -dev variants, copying application artifacts into a final minimal container that offers a reduced attack surface that won’t allow package installations or logins.

Learn More

To better understand how to work with Chainguard Containers, please visit Chainguard Academy and Chainguard Courses.

In addition to Containers, Chainguard offers VMs and Libraries. Contact Chainguard to access additional products.

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.