Chainguard Container for sealed-secrets-kubeseal

A Kubernetes tool that uses one-way encryption of Secrets, enabling safe GitOps-friendly secret management.

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/sealed-secrets-kubeseal: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 Sealed Secrets Kubeseal Chainguard image is comparable to the official Sealed Secrets Kubeseal image from Docker Hub.

Getting Started

Sealed Secrets is typically used alongside GitOps workflows to safely manage encrypted Kubernetes Secrets.

Encrypting Secrets with Docker

The sealed-secrets-kubeseal image can be used to encrypt and/or validate the sealed secrets.

To seal a secret, run the image and mount the Kubernetes config file - such as:

docker run \
  -v $KUBECONFIG:/.kube/config:ro \
  -e KUBECONFIG=/.kube/config \
  cgr.dev/ORGANIZATION/sealed-secrets-kubeseal \
  -o yaml \
  <secret.yaml >sealed-secret.yaml

This will encrypt contents of secret.yaml as sealed-secret.yaml.

It's also possible to validate a sealed secret using the --validate flag to make sure the sealed secret is correct - such as:

docker run \
  -v $KUBECONFIG:/.kube/config:ro \
  -e KUBECONFIG=/.kube/config \
  cgr.dev/ORGANIZATION/sealed-secrets-kubeseal \
  --validate \
  <sealed-secret.yaml

Applying Sealed Secrets

Once encrypted, apply the SealedSecret to your cluster:

kubectl apply -f sealed-secret.yaml

Sealed secrets controller needs to be running in the cluster for this to work. The sealed-secrets-controller Chainguard image can be used for this purpose.

Documentation and Resources

Please refer to the [upstream documentation] (https://github.com/bitnami-labs/sealed-secrets) for more details.

For configuration options and full documentation, refer to the Sealed Secrets Helm Chart on Artifact Hub.

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.