/
DirectorySecurity Advisories
Sign In
Directory
contour-fips logoFIPS

contour-fips

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

The Chainguard Contour image is comparable to the official Docker Hub image. It 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.

Deployment

Please refer to the Contour getting started documentation, for installation steps, which includes 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

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

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

  • GCC-exception-3.1

  • GPL-3.0-or-later

  • 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

Compliance

This is a FIPS validated image for FedRAMP compliance.

This image is STIG hardened and scanned against the DISA General Purpose Operating System SRG with reports available.

Learn more about STIGsGet started with STIGs

Related images

Category
FIPS
STIG
application

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

Product

Chainguard Images