openstack-heat-oshelm-fips

packaged by Chainguard

Chainguard Container for openstack-heat-oshelm-fips

FIPS variant of openstack-heat-oshelm, built against FIPS-validated OpenSSL.

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/openstack-heat-oshelm-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

cgr.dev/ORGANIZATION/openstack-heat-oshelm-fips is the FIPS variant of openstack-heat-oshelm, a minimal, distroless drop-in for quay.io/airshipit/heat, the image the openstack-helm heat chart targets by default. It follows the same chart contract: it runs as UID 42424, serves every heat workload the chart deploys (heat-api and heat-cfn under uwsgi, heat-engine, db-sync, engine-cleaner, and purge-deleted), and exposes the service virtualenv at /var/lib/openstack with /var/lib/openstack/bin first on PATH. See the openstack-heat-oshelm documentation for the details of that contract.

The image stream tracks the OpenStack 2026.1 (Gazpacho) release and corresponds to the openstack-heat-2026.1 apk package group.

FIPS support

The openstack-heat-oshelm-fips Chainguard Container ships with a validated redistribution of OpenSSL's FIPS provider module. For more on FIPS support in Chainguard Containers, consult the guide on FIPS-enabled Chainguard Containers on Chainguard Academy.

Heat's own cryptography works unchanged under the FIPS provider: the engine loads every resource type, stored credentials are encrypted with Fernet (AES and HMAC-SHA256), OS::Heat::RandomString uses the system CSPRNG, Swift signal URLs are signed with HMAC-SHA256, and the CloudFormation-compatible API forwards EC2 signatures to Keystone, which verifies them with HMAC. The differences are:

• The str_digest template function refuses blake2b and blake2s, which are not FIPS-approved, so a stack that uses them fails to create. md5 keeps working only because the image enables the OpenSSL legacy provider by default; with CHAINGUARD_LEGACY_ALLOWED=0 it is refused too. The sha* and sha3_* algorithms work in both modes.
• MariaDB ed25519_password authentication is not supported: pymysql needs PyNaCl for it, which bundles libsodium, and libsodium has no FIPS-validated module. Use another authentication plugin for the heat database user.
• Do not enable oslo.middleware HTTP basic authentication (http_basic_auth_user_file): it verifies bcrypt hashes, and bcrypt is not FIPS-approved. The chart's api-paste.ini pipelines do not use it.
• Use TLS for the database and RabbitMQ connections. Plaintext connections work, but then that traffic, including credentials, is not protected by the FIPS provider.
• Deploy it with FIPS variants of the services it talks to, starting with openstack-keystone-oshelm-fips. This image only makes heat's own processes FIPS-compliant.

Prerequisites

Heat needs Keystone, MariaDB, and RabbitMQ, and the chart creates the trusts and the stack-user domain it needs through Keystone. The resources a stack can create depend on the services in the catalog: nova, neutron, cinder, and glance for the common OS::* resource types. Use FIPS variants of those services where they exist. See upstream's deploy-compute-kit.yaml playbook for a full deployment.

Getting Started

Point every heat image slot of the chart at this image and give the chart registry credentials for cgr.dev (a pull token). The chart attaches imagePullSecrets to its pods only when endpoints.oci_image_registry.auth.enabled is set. Create a values.yaml:

cat > values.yaml <<EOF
endpoints:
  oci_image_registry:
    auth:
      enabled: true
      heat:
        username: <pull-token-username>
        password: <pull-token-password>
    host_fqdn_override:
      default: cgr.dev
images:
  tags:
    heat_db_sync: cgr.dev/ORGANIZATION/openstack-heat-oshelm-fips:2026.1
    heat_api: cgr.dev/ORGANIZATION/openstack-heat-oshelm-fips:2026.1
    heat_cfn: cgr.dev/ORGANIZATION/openstack-heat-oshelm-fips:2026.1
    heat_engine: cgr.dev/ORGANIZATION/openstack-heat-oshelm-fips:2026.1
    heat_engine_cleaner: cgr.dev/ORGANIZATION/openstack-heat-oshelm-fips:2026.1
    heat_purge_deleted: cgr.dev/ORGANIZATION/openstack-heat-oshelm-fips:2026.1
EOF

Then install the chart from the openstack-helm repository:

helm repo add openstack-helm https://tarballs.opendev.org/openstack/openstack-helm
helm upgrade --install heat openstack-helm/heat --namespace openstack --values values.yaml

The chart's other image slots (the bootstrap, database, keystone, and trusts jobs) use the openstack-client image, the RabbitMQ init job uses the rabbitmq image, and the dependency-check init containers, Rally test pod, and image sync job use their own images; they are unaffected.

Configuration

Configuration comes from the chart, which renders heat.conf, api-paste.ini, policy.yaml, and the uwsgi configurations and mounts them under /etc/heat/. See the openstack-helm heat chart and the upstream Heat configuration reference for the full set of options.

Documentation and Resources

• OpenStack Heat documentation
• openstack-helm documentation
• FIPS-enabled Chainguard Containers

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.