Last changed
Be the first to hear about exciting product updates, critical vulnerability alerts, compare alternative images, and more.
Sign UpA Kubernetes controller and tool for one-way encrypted Secrets, enabling safe GitOps-friendly secret management.
Chainguard Containers are regularly-updated, secure-by-default container images.
For those with access, this container image is available on cgr.dev
:
Be sure to replace the ORGANIZATION
placeholder with the name used for your organization's private repository within the Chainguard Registry.
The Sealed Secrets Controller Chainguard image is comparable to the official Sealed Secrets Controller image from Docker Hub.
Sealed Secrets is typically used alongside GitOps workflows to safely manage encrypted Kubernetes Secrets.
Sealed Secrets is designed to run as a native Kubernetes controller.
To deploy sealed secrets with the Chainguard image, create a values.yaml
file with the image information - such as:
Then install the controller using Helm:
This deploys the Sealed Secrets controller in the kube-system
namespace using the specified image. This is the default namespace that kubeseal
tool for encrypting secrets is expected, so changing the namespace will also require providing --controller-namespace
argument to kubeseal
whenever encrypting a secret.
To encrypt a secret, use the kubectl
to create a Kubernetes Secret YAML file (unless you already have it) and then use kubeseal
CLI tool to encrypt it. Such as:
This generates a SealedSecret
that can be safely committed to version control.
Once encrypted, apply the SealedSecret to your cluster:
The controller will decrypt it and create the actual Kubernetes Secret.
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.
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:
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.
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.
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.
Chainguard container images contain software packages that are direct or transitive dependencies. The following licenses were found in the "latest" tag of this image:
Apache-2.0
LGPL-2.1-or-later
MIT
MPL-2.0
For a complete list of licenses, please refer to this Image's SBOM.
Software license agreement