Chainguard Container for headlamp-plugin-flux-fips

Headlamp plugin to visualize and manage Flux GitOps resources in Kubernetes clusters.

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/headlamp-plugin-flux-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 headlamp-plugin-flux-fips container image is a drop-in replacement for the upstream headlamp-k8s/headlamp-plugin-flux image. The Flux plugin provides a way to visualize Flux in Headlamp. Like the upstream image, when installed, the plugin adds a new item (Flux) to the Headlamp sidebar, enabling users to visualize and manage Flux GitOps resources such as GitRepositories and Kustomizations directly through the Headlamp UI. This image is designed to be a minimal, secure alternative that runs as a non-root user. Switching to this image should not require any changes to your existing deployment configuration.

FIPS Support

The headlamp-plugin-flux-fips Chainguard Container 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

You can deploy this image using the Headlamp Helm chart. To enable the Flux plugin, override the chart values to add an initContainer that copies the plugin into Headlamp’s plugin directory.

Be sure to override the image by setting the following values in a values.yaml file:

initContainers:
  - name: flux-plugin
    image: cgr.dev/ORGANIZATION/headlamp-plugin-flux-fips:latest
    imagePullPolicy: Always
    command: ["/bin/sh", "-c"]
    args:
      - "mkdir -p /headlamp/plugins && cp -r /plugins/* /headlamp/plugins/ && chown -R 100:101 /headlamp/plugins"
    securityContext:
      runAsNonRoot: false
      privileged: false
      runAsUser: 0
      runAsGroup: 0
    volumeMounts:
      - mountPath: /headlamp/plugins
        name: headlamp-plugins

volumes:
  - name: headlamp-plugins
    emptyDir: {}

volumeMounts:
  - mountPath: /headlamp/plugins
    name: headlamp-plugins

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard registry.

Then, install Headlamp with these values

helm repo add headlamp https://kubernetes-sigs.github.io/headlamp/
helm repo update
helm install headlamp headlamp/headlamp --namespace headlamp --create-namespace --values values.yaml --wait

Documentation and Resources

• Headlamp Plugins Github Repository
• Headlamp Github Repository
• Headlamp Helm Charts

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.