keda-http-add-on-scaler-fips

packaged by Chainguard

Chainguard Container for keda-http-add-on-scaler-fips

A FIPS-compliant image for kedacore-http-add-on. Add-on for KEDA that enables event-driven autoscaling of HTTP workloads on Kubernetes, including scale-to-zero.

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/keda-http-add-on-scaler-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

This is the FIPS-compliant variant of the KEDA HTTP Add-on, built with a FIPS 140-validated Go cryptographic module (openssl-config-fipshardened). It is comprised of three container images:

• cgr.dev/ORGANIZATION/keda-http-add-on-operator-fips
• cgr.dev/ORGANIZATION/keda-http-add-on-interceptor-fips
• cgr.dev/ORGANIZATION/keda-http-add-on-scaler-fips

Chainguard's KEDA HTTP Add-on FIPS images are drop-in replacements for the upstream ghcr.io/kedacore/http-add-on-* images for workloads that require FIPS-validated cryptography. These imagse are designed to be a minimal, secure alternative that runs as a non-root user. Switching to these Chainguard images should not require any changes to your existing setup.

Getting Started

The HTTP Add-on requires KEDA core to be installed in the cluster. If you require end-to-end FIPS compliance, install the FIPS variant of the KEDA core images as well. Once KEDA is running, deploy the HTTP Add-on with the upstream Helm chart, overriding the image references to point at Chainguard's FIPS registry paths.

Prerequisites

• A Kubernetes cluster with KEDA installed (the HTTP Add-on depends on KEDA's ScaledObject CRD).
• Helm v3.

Deployment using Helm Chart

Install the HTTP Add-on chart with Chainguard's FIPS images:

helm repo add kedacore https://kedacore.github.io/charts
helm repo update

helm install http-add-on kedacore/keda-add-ons-http \
  --namespace keda \
  --set images.operator=cgr.dev/ORGANIZATION/keda-http-add-on-operator-fips \
  --set images.interceptor=cgr.dev/ORGANIZATION/keda-http-add-on-interceptor-fips \
  --set images.scaler=cgr.dev/ORGANIZATION/keda-http-add-on-scaler-fips \
  --set images.tag=latest

Wait for all three deployments to roll out:

kubectl -n keda rollout status deploy/keda-add-ons-http-controller-manager
kubectl -n keda rollout status deploy/keda-add-ons-http-interceptor
kubectl -n keda rollout status deploy/keda-add-ons-http-external-scaler

To confirm FIPS mode is active, each container exits non-zero on startup when GODEBUG=fips140=on is set but the FIPS module is unavailable — running the container with a tampered OpenSSL FIPS module file and observing the panic is the canonical integrity check.

Routing HTTP traffic to a scale-to-zero workload

Once deployed, the user-facing CRDs and traffic flow are identical to the non-FIPS variant. Declare an InterceptorRoute plus a KEDA ScaledObject against your backend Service:

apiVersion: http.keda.sh/v1beta1
kind: InterceptorRoute
metadata:
  name: my-app
  namespace: my-app-ns
spec:
  target:
    service: my-app
    port: 80
  rules:
    - hosts:
        - my-app.example.com
  scalingMetric:
    concurrency:
      targetValue: 100
---
apiVersion: keda.sh/v1alpha1
kind: ScaledObject
metadata:
  name: my-app
  namespace: my-app-ns
spec:
  scaleTargetRef:
    name: my-app
  minReplicaCount: 0
  maxReplicaCount: 10
  triggers:
    - type: external-push
      metadata:
        scalerAddress: keda-add-ons-http-external-scaler.keda:9090
        interceptorRoute: my-app

Send traffic through the interceptor's proxy Service (keda-add-ons-http-interceptor-proxy); requests arriving while the backend is scaled to zero are buffered until KEDA scales it back up.

Documentation and Resources

• KEDA core documentation
• Upstream kedacore/http-add-on releases
• Helm chart reference
• Chainguard FIPS documentation

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.