packaged by Chainguard
Contact our team to test out this image for free. Please also indicate any other images you would like to evaluate.
Minimal kro image for defining and managing groups of Kubernetes resources.
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 kro image is comparable to registry.k8s.io/kro/kro and preserves its /ko-app/controller entrypoint and command-line interface. It runs as UID 65532 by default instead of the upstream image's UID 0. The upstream Helm chart's UID 1000 security context is also supported.
You need a Kubernetes cluster, Helm 3, kubectl, and permissions to install CRDs and cluster-wide RBAC. Configure the cluster to pull cgr.dev/ORGANIZATION/kro with your organization's registry credentials. See the upstream installation guide for supported deployment methods.
Replace ORGANIZATION with your registry organization, then create a values file that selects the Chainguard image:
If your cluster uses an image pull secret, add its name to imagePullSecrets in the values file. To select a specific release, set image.tag to that release and pass the corresponding chart version with --version.
The controller is ready to reconcile resources. Follow the upstream ResourceGraphDefinition walkthrough to define an API, create an instance, and inspect the resources it manages.
The chart configures /healthz and /readyz probes on port 8079. Use the chart values to configure leader election, resource limits, reconciliation concurrency, and image pull secrets.
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:
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.
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.
Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.
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's 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
CC-PDDC
LGPL-2.1-or-later
MIT
MPL-2.0
For a complete list of licenses, please refer to this Image's SBOM.
Software license agreementChainguard Containers are SLSA Level 3 compliant with detailed metadata and documentation about how it was built. We generate build provenance and a Software Bill of Materials (SBOM) for each release, with complete visibility into the software supply chain.
SLSA compliance at ChainguardThis image helps reduce time and effort in establishing PCI DSS 4.0 compliance with low-to-no CVEs.
PCI DSS at ChainguardA FIPS validated version of this image is available for FedRAMP compliance. STIG is included with FIPS image.