openstack-placement-api-kolla-fips

packaged by Chainguard

Chainguard Container for openstack-placement-api-kolla-fips

FIPS variant of openstack-placement-api-kolla — same image set, 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-placement-api-kolla-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-validated variant of openstack-placement-api-kolla — the same version-streamed, distroless kolla placement-api image set, but built against FIPS-validated OpenSSL via the openstack-placement-<stream>-fips apks and shipping the hardened OpenSSL configuration (openssl-config-fipshardened). It is a drop-in replacement for the upstream openstack.kolla/placement-api image when consumed by kolla-ansible or kayobe.

The OpenStack Placement service exposes a REST API (placement-api) that tracks resource providers and their inventories (VCPU, memory, disk), allocations, and traits across a cloud; Nova consults it before every scheduling decision. The runtime contract is identical to the non-FIPS image: dumb-init runs as PID 1 and wraps kolla_start, which reads the bind-mounted /var/lib/kolla/config_files/config.json, invokes kolla_set_configs, then execs the configured command (the placement WSGI application). Because kolla_start is the image CMD rather than its entrypoint, kolla-ansible can override it for one-shot bootstrap containers such as the placement db-sync job.

Each image stream tracks the OpenStack release cycle (e.g. 2026.1 Gazpacho) and corresponds to the openstack-placement-<stream>-fips apk package group, pinning to the matching placement release series.

FIPS Support

The openstack-placement-api-kolla-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.

Getting Started

The image is configured entirely through kolla's config.json mechanism: mount your rendered configuration under /var/lib/kolla/config_files/ and set KOLLA_CONFIG_STRATEGY to COPY_ONCE (copy at first start) or COPY_ALWAYS (copy on every start). On boot, kolla_set_configs copies each entry to its destination with the requested ownership and permissions, then the placement API is served.

In a real deployment you almost always drive this through kolla-ansible, pointing the placement-api image at the Chainguard FIPS build:

# kolla-ansible globals.yml / group_vars
placement_api_image_full: "cgr.dev/ORGANIZATION/openstack-placement-api-kolla-fips:2026.1"

The image is equally compatible with the upstream openstack-helm placement chart for Kubernetes deployments — override the chart's images.tags.placement and images.tags.placement_db_sync values with this image.

Configuration

Placement is configured by a standard placement.conf (plus policy and migration files) delivered via the config.json payload described above. See the upstream kolla-ansible placement role for canonical examples of the rendered configuration, and the placement configuration reference for the complete set of options.

Upstream Equivalent

Documentation and Resources

• OpenStack Placement documentation
• Placement API reference
• Placement configuration reference
• kolla-ansible placement role
• openstack-helm placement chart

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.