DirectorySecurity Advisories
Sign In
Directory
knative-serving-queue logo

knative-serving-queue

Last changed

Create your Free Account

Be the first to hear about exciting product updates, critical vulnerability alerts, compare alternative images, and more.

Sign Up
Versions
Overview
Provenance
Specifications
SBOM
Vulnerabilities
Advisories

Chainguard Image for knative-serving-queue

Knative Serving builds on Kubernetes to support deploying and serving of applications and functions as serverless containers.

Chainguard Images are regularly-updated, minimal container images with low-to-zero CVEs.

Download this Image

This image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/knative-serving-queue: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 official Knative Serving image includes multiple components, including activator, autoscaler, and queue. The Chainguard Knative Serving Image only provides an image for the queue component of the Knative Serving, whcih is comparable to the Knative Serving Queue Image from Google Container Registry. However, the Chainguard image does not run as the root user and contains only the minimum set of tools and dependencies needed to function. This means it doesn't include things like a shell or a package manager.

Getting Started

There are multiple ways of deploying Knative Serving on Kubernetes cluster. One of the ways is to use the official Knative Operator and the other way is to use the plain YAML manifests.

In order to deploy Knative Serving using the plain YAML manifests, you will first need to install the CRDs:

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

Then you can install the Knative Serving components:

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

Once you have the Knative Serving components installed, be sure to change the image for the Knative Serving Queue component using the following command:

cat <<'EOX' | kubectl apply -f-
apiVersion: caching.internal.knative.dev/v1alpha1
kind: Image
metadata:
  name: queue-proxy
  namespace: knative-serving
  labels:
    app.kubernetes.io/component: queue-proxy
    app.kubernetes.io/name: knative-serving
    app.kubernetes.io/version: ${local.version_without_epoch}
spec:
  image: cgr.dev/ORGANIZATION/knative-serving-queue:latest
EOX

Additionally, you should should patch the configmap where Knative defined the image for the queue component:

kubectl patch configmap config-deployment -n knative-serving --type=json -p='[{"op": "replace", "path": "/data/queue-sidecar-image", "value": "cgr.dev/ORGANIZATION/knative-serving-queue:latest"}]'

The next steps would be installing the network layer and configuring the DNS.

Once you install the network layer and configure the DNS, you can deploy your first Knative service using kn:

kn service create hello \
--image ghcr.io/knative/helloworld-go:latest \
--port 8080 \
--env TARGET=World

Then you should be able to access your service using the following command:

URL=$(kn service describe hello -ojson | jq -r '.status.url')
curl $URL

You should see the following output:

Hello World!

For more information on deploying Knative Serving with yaml files, refer to the official Knative Serving documentation:

Documentation and Resources

Contact Support

If you have a Zendesk account (typically set up for you by your Customer Success Manager) you can reach out to Chainguard's Customer Success team through our Zendesk portal.

What are Chainguard Images?

Chainguard Images are a collection of container images designed for security and minimalism.

Many Chainguard Images are distroless; they contain only an open-source application and its runtime dependencies. These images do not even contain a shell or package manager. Chainguard Images are built with Wolfi, our Linux undistro designed to produce container images that meet the requirements of a secure software supply chain.

The main features of Chainguard Images include:

-dev Variants

As mentioned previously, Chainguard’s distroless Images have no shell or package manager by default. This is great for security, but sometimes you need these things, especially in builder images. For those cases, most (but not all) Chainguard Images come paired with a -dev variant which does include a shell and package manager.

Although the -dev image variants have similar security features as their distroless versions, such as complete SBOMs and signatures, they feature additional software that is typically not necessary in production environments. The general recommendation is to use the -dev variants only to build the application and then copy all application artifacts into a distroless image, which will result in a final container image that has a minimal attack surface and won’t allow package installations or logins.

That being said, it’s worth noting that -dev variants of Chainguard Images are completely fine to run in production environments. After all, the -dev variants are still more secure than many popular container images based on fully-featured operating systems such as Debian and Ubuntu since they carry less software, follow a more frequent patch cadence, and offer attestations for what they include.

Learn More

To better understand how to work with Chainguard Images, we encourage you to visit Chainguard Academy, our documentation and education platform.

Licenses

Chainguard Images contain software packages that are direct or transitive dependencies. The following licenses were found in the "latest" version 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 agreement

Category
application

Safe Source for Open Sourceâ„¢
Media KitContact Us
© 2024 Chainguard. All Rights Reserved.
Private PolicyTerms of Use

Product

Chainguard Images