Chainguard Container for knative-operator

Combined operator for Knative.

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-operator: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 Operator image includes multiple components, including operator and webhook. The Chainguard Operator Image provides images for the operator and webhook components of the Knative Operator, which are comparable to the Knative Operator 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

The Knative Operator image of Chainguard provides the following images for each of the component of Knative Operator:

• cgr.dev/ORGANIZATION/knative-operator:latest
• cgr.dev/ORGANIZATION/knative-operator-webhook:latest

To get started with the Knative Operator, you can use the following Helm chart to install the Knative Operator on your Kubernetes cluster.

You can use the following values.yaml file to install the Knative Operator using Helm basically:

cat <<EOF > knative-operator-values.yaml
knative_operator:
  knative_operator:
    image: cgr.dev/ORGANIZATION/knative-operator
    tag: latest
  operator_webhook:
    image: cgr.dev/ORGANIZATION/knative-operator-webhook
    tag: latest
EOF

then run the following command:

helm repo add knative-operator https://knative.github.io/operator
helm install knative-operator knative-operator/knative-operator -f knative-operator-values.yaml

This will install the Knative Operator on your Kubernetes cluster.

After the installation, you can check the status of the Knative Operator by running the following command:

kubectl get pods -n knative-operator

Once the Knative Operator is up and running, you can start using it to install Knative components on your Kubernetes cluster like Knative Serving, Knative Eventing, and Knative Monitoring.

For example to install Knative Serving, you can use the following command:

cat <<EOF | kubectl apply -f -
apiVersion: v1
kind: Namespace
metadata:
  name: knative-serving
---
apiVersion: operator.knative.dev/v1beta1
kind: KnativeServing
metadata:
  name: knative-serving
  namespace: knative-serving
EOF

NOTE: If you would like to do some customizations to the Knative Serving installation, you can refer to the Knative Serving documentation.

After a few seconds, you can check the status of the Knative Serving by running the following command:

bash-5.2# kubectl get knativeservings -n knative-serving
NAME              VERSION             READY   REASON
knative-serving   <version number>    True
bash-5.2#

Documentation and Resources

• Installing Knative components with Knative Operator

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.