extension-auto-registration-kubernetes-fips

packaged by Chainguard

Chainguard Container for extension-auto-registration-kubernetes-fips

Steadybit sidecar that discovers extensions in Kubernetes and registers them with the local agent, built with FIPS-validated cryptography

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/extension-auto-registration-kubernetes-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 image is built from source with Chainguard's FIPS Go toolchain and is designed as a drop-in replacement for the upstream ghcr.io/steadybit/extension-auto-registration-kubernetes image. All cryptography, including TLS to the Kubernetes API, goes through the Go standard library, which the FIPS toolchain routes to a FIPS-validated OpenSSL module. The extension binary is available at /extension, the same path the upstream image uses as its entrypoint.

The image runs as the steadybit user (UID 10000), matching the upstream image. It does not expose any ports: the extension is an outbound client that watches pods and services through the Kubernetes API and registers discovered Steadybit extensions with the Steadybit agent on localhost.

Getting Started

The extension usually runs as a sidecar of the Steadybit agent, deployed by the steadybit-agent Helm chart. To use the Chainguard image, create a values file that overrides the auto-registration image and raises the sidecar's memory limit:

cat > values.yaml <<EOF
agent:
  key: "<your-agent-key>"
  extensions:
    autoregistration:
      image:
        registry: cgr.dev
        name: ORGANIZATION/extension-auto-registration-kubernetes-fips
        tag: latest
      resources:
        limits:
          memory: 128Mi
EOF

Then install the chart with the values file:

helm repo add steadybit https://steadybit.github.io/helm-charts
helm repo update

helm install steadybit-agent steadybit/steadybit-agent \
  --namespace steadybit --create-namespace \
  --values values.yaml

The FIPS build uses more memory than the standard image. With the chart's default agent.extensions.autoregistration.resources.limits.memory of 50Mi, the FIPS sidecar can be OOM-killed and restarted. Raise the limit to at least 128Mi, as shown in the values file above.

The extension needs a service account with get, list, and watch permissions on pods and services. The Helm chart creates these RBAC resources for you.

Configuration

The extension is configured through environment variables, such as STEADYBIT_EXTENSION_AGENT_KEY, STEADYBIT_EXTENSION_AGENT_PORT (default 42899), STEADYBIT_EXTENSION_NAMESPACE_FILTER, and STEADYBIT_LOG_LEVEL. Refer to the upstream README for the full list of options.

Documentation and Resources

• Steadybit extension-auto-registration-kubernetes on GitHub
• Steadybit Helm charts
• Steadybit 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.