openstack-heat-oshelm

packaged by Chainguard

Chainguard Container for openstack-heat-oshelm

Minimal OpenStack Heat image compatible with the upstream openstack-helm heat image.

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:latest

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

Compatibility Notes

Minimal, distroless OpenStack Heat image for openstack-helm, compatible with the upstream airshipit/heat image the heat chart targets by default.

• The image runs as the heat account (uid/gid 42424, home /var/lib/heat) by default, where the upstream image runs as root. This matches the chart's runAsUser for the APIs, the engine, and the engine-cleaner CronJob. The db-sync job and the purge-deleted CronJob set none, so they now run as heat instead of root.
• One image serves every heat workload the chart deploys: the heat-api and heat-cfn Deployments (the Orchestration and CloudFormation-compatible APIs under uwsgi), heat-engine, the db-sync job, and the engine-cleaner and purge-deleted CronJobs.
• The service lives in a release-scoped virtualenv and is exposed at /var/lib/openstack, with /var/lib/openstack/bin first on PATH — the layout the chart assumes when it invokes bare uwsgi, heat-engine, and heat-manage.
• Apache and mod_wsgi are not included. The upstream image ships them, but the chart serves both APIs with uwsgi.

Each image stream tracks the OpenStack release cycle (e.g. 2026.1 Gazpacho) and corresponds to the openstack-heat-<stream> apk package group.

Getting Started

Point every heat image slot of the chart at this image with a values.yaml:

images:
  tags:
    heat_db_sync: cgr.dev/ORGANIZATION/openstack-heat-oshelm:2026.1
    heat_api: cgr.dev/ORGANIZATION/openstack-heat-oshelm:2026.1
    heat_cfn: cgr.dev/ORGANIZATION/openstack-heat-oshelm:2026.1
    heat_engine: cgr.dev/ORGANIZATION/openstack-heat-oshelm:2026.1
    heat_engine_cleaner: cgr.dev/ORGANIZATION/openstack-heat-oshelm:2026.1
    heat_purge_deleted: cgr.dev/ORGANIZATION/openstack-heat-oshelm:2026.1

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.

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. See upstream's deploy-compute-kit.yaml playbook for a full deployment.

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
• openstack-helm heat chart
• Upstream airshipit/heat Dockerfile

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.