knative-serving-fips-controller

packaged by Chainguard

Chainguard Container for knative-serving-fips

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

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/knative-serving-fips: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 images includes multiple components, including activator, autoscaler, controller, webhook and queue. The Chainguard Knative Serving Images provides images for all component of the Knative Serving, which are comparable to the Knative Serving Queue Image from Google Container Registry. However, the Chainguard images 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:

# Example for v1.18.1
kubectl apply -f https://github.com/knative/serving/releases/download/knative-v1.18.1/serving-crds.yaml

Then you can install the Knative Serving components:

kubectl apply -f https://github.com/knative/serving/releases/download/knative-v1.18.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-fips:latest
---
apiVersion: caching.internal.knative.dev/v1alpha1
kind: Image
metadata:
  name: activator
  namespace: knative-serving
  labels:
    app.kubernetes.io/component: activator
    app.kubernetes.io/name: knative-serving
    app.kubernetes.io/version: ${local.version_without_epoch}
spec:
  image: cgr.dev/ORGANIZATION/knative-serving-activator-fips:latest
---
apiVersion: caching.internal.knative.dev/v1alpha1
kind: Image
metadata:
  name: autoscaler
  namespace: knative-serving
  labels:
    app.kubernetes.io/component: autoscaler
    app.kubernetes.io/name: knative-serving
    app.kubernetes.io/version: ${local.version_without_epoch}
spec:
  image: cgr.dev/ORGANIZATION/knative-serving-autoscaler-fips:latest
---
apiVersion: caching.internal.knative.dev/v1alpha1
kind: Image
metadata:
  name: controller
  namespace: knative-serving
  labels:
    app.kubernetes.io/component: controller
    app.kubernetes.io/name: knative-serving
    app.kubernetes.io/version: ${local.version_without_epoch}
spec:
  image: cgr.dev/ORGANIZATION/knative-serving-controller-fips:latest
---
apiVersion: caching.internal.knative.dev/v1alpha1
kind: Image
metadata:
  name: webhook
  namespace: knative-serving
  labels:
    app.kubernetes.io/component: webhook
    app.kubernetes.io/name: knative-serving
    app.kubernetes.io/version: ${local.version_without_epoch}
spec:
  image: cgr.dev/ORGANIZATION/knative-serving-webhook-fips: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:

NOTE: You need to install the kn CLI tool to deploy your first Knative service. To do this, refer to these installation instructions.

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

• (Blog) Install Knative using quickstart

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.