Chainguard Container for net-kourier

Knative Ingress implementation using Envoy

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/net-kourier: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 net-kourier image is a Chainguard-built image for the official Knative net-kourier ingress controller. This image maintains full compatibility with upstream Knative image.

There are no breaking changes from the upstream Knative net-kourier functionality.

Prerequisites

To use the net-kourier image, you'll need:

• A Kubernetes cluster (version 1.24 or later)
• Knative Serving installed
• kubectl configured to communicate with your cluster

For detailed installation requirements, refer to the official Knative documentation.

Getting Started

The net-kourier image serves as the ingress controller for Knative Serving. It's typically deployed as part of the Knative networking layer rather than run directly.

Installing with Knative Serving

First, install Knative Serving CRDs and core components:

kubectl apply -f https://github.com/knative/serving/releases/latest/download/serving-crds.yaml
kubectl apply -f https://github.com/knative/serving/releases/latest/download/serving-core.yaml

Next, install the Kourier networking layer, with Chainguard image:

wget https://github.com/knative/net-kourier/releases/latest/download/kourier.yaml
yq eval '(select(.kind == "Deployment" and .metadata.name == "net-kourier-controller") | .spec.template.spec.containers[0].image) = cgr.dev/ORGANIZATION/net-kourier:latest' -i kourier.yaml
kubectl apply -f kourier.yaml

Configure Knative to use Kourier as the ingress:

kubectl patch configmap/config-network \
  --namespace knative-serving \
  --type merge \
  --patch '{"data":{"ingress.class":"kourier.ingress.networking.knative.dev"}}'

Now you can verify the installation and check that the Kourier components are running:

kubectl get pods -n knative-serving
kubectl get pods -n kourier-system

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.