Chainguard Container for contour-fips

Contour is an ingress controller for Kubernetes that works by deploying the Envoy proxy as a reverse proxy and load balancer. Contour supports dynamic configuration updates out of the box while maintaining a lightweight profile.

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/contour-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

Chainguard's contour-fips container image is comparable to the official Contour image. The Chainguard image runs as a non-root user (65532) and includes only the essential tools and dependencies needed to function, omitting extras like a package manager or shell.

Envoy dependency

Contour is a Kubernetes ingress controller that deploys Envoy as a reverse proxy and load balancer. The Kubernetes manifest provided in the Contour quick start guide deploys both Contour and Envoy.

If you also require a Chainguard image for Envoy, you can find this in our image catalog.

FIPS support

The contour-fips Chainguard Image ships with a validated redistribution of OpenSSL's FIPS provider module. For more on FIPS support in Chainguard Images, consult the guide on FIPS-enabled Chainguard Images on Chainguard Academy.

Getting Started

Please refer to the Contour getting started documentation, for installation steps, which include a Kubernetes manifest.

You'll need to either create your own modified copy of the manifest or, alternatively, use a tool such as Kustomize to replace the images.

Example using Kustomize:

cat <<EOF >kustomization.yaml
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization

resources:
- https://projectcontour.io/quickstart/contour.yaml

images:
- name: ghcr.io/projectcontour/contour
  newName: cgr.dev/ORGANIZATION/contour-fips
  newTag: latest
- name: docker.io/envoyproxy/envoy
  newName: cgr.dev/ORGANIZATION/envoy-fips
  newTag: latest
EOF

kubectl apply -k .

If you are testing Contour in a local Kubernetes environment, such ask3d or kind, you may run into port conflict issues. To work around this, you'll need to set alternative hostPorts for envoy.

Here is another example using kustomize:

cat <<EOF >kustomization.yaml
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization

resources:
- https://projectcontour.io/quickstart/contour.yaml

images:
- name: ghcr.io/projectcontour/contour
  newName: cgr.dev/ORGANIZATION/contour-fips
  newTag: latest
- name: docker.io/envoyproxy/envoy
  newName: cgr.dev/ORGANIZATION/envoy-fips
  newTag: latest

patches:
- patch: |
    apiVersion: apps/v1
    kind: DaemonSet
    metadata:
      name: envoy
      namespace: projectcontour
    spec:
      template:
        spec:
          containers:
          - name: envoy
            ports:
            - containerPort: 8080
              hostPort: 8082
              name: http
              protocol: TCP
            - containerPort: 8443
              hostPort: 8445
              name: https
              protocol: TCP
EOF

kubectl apply -k .

Following successful deployment, you should see Contour and Envoy running in the cluster:

kubectl get po -n projectcontour

NAME                            READY   STATUS      RESTARTS   AGE
contour-69c98d9c8-v8fl7         1/1     Running     0          8m42s
contour-69c98d9c8-x5s48         1/1     Running     0          8m42s
contour-certgen-v1-30-2-z7lzk   0/1     Completed   0          8m42s
envoy-ql79l                     2/2     Running     0          8m42s

Documentation and Resources

For more information on Contour, including some follow-on steps on how to validate the installation, please refer to Getting started with Contour.

What are Chainguard Containers?

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:

• 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 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.

Need additional packages?

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.

Learn More

Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.

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.