openstack-designate-oshelm-fips

packaged by Chainguard

Chainguard Container for openstack-designate-oshelm-fips

FIPS variant of openstack-designate-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-designate-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-designate-oshelm-fips is the FIPS variant of openstack-designate-oshelm, a minimal, distroless drop-in for quay.io/airshipit/designate, the image the openstack-helm designate chart targets by default. It follows the same chart contract: it runs as UID 42424, serves every designate workload the chart deploys (designate-api under uwsgi, designate-central, designate-mdns, designate-worker, designate-producer, designate-sink, db-sync, and service-cleaner), and exposes the service virtualenv at /var/lib/openstack with /var/lib/openstack/bin first on PATH. See the openstack-designate-oshelm documentation for the details of that contract.

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

FIPS support

The openstack-designate-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.

The image uses the same designate packages as openstack-designate-oshelm: they ship no PyNaCl and no bundled OpenSSL, and cryptography, pyOpenSSL and psycopg2 come from Chainguard's system packages. The differences under FIPS are:

• Designate keys each record with an MD5 hash (hashlib.md5(usedforsecurity=False)) to detect duplicates. This works because the image enables the OpenSSL legacy provider by default; with CHAINGUARD_LEGACY_ALLOWED=0, MD5 is unavailable and creating records fails.
• Use hmac-sha256 or stronger for TSIG keys; hmac-md5 is not FIPS-approved.
• 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 designate 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 designate's own processes FIPS-compliant.

Prerequisites

The prerequisites are those of openstack-designate-oshelm: MariaDB, RabbitMQ, Memcached, Keystone, and openstack-helm's powerdns chart (for the default pool) in the openstack namespace before you install designate. Use FIPS variants of those services where they exist.

Getting Started

Write a values.yaml that points every designate image slot of the chart at this image and gives 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:

endpoints:
  oci_image_registry:
    auth:
      enabled: true
      designate:
        username: <pull-token-username>
        password: <pull-token-password>
    host_fqdn_override:
      default: cgr.dev
images:
  tags:
    designate_db_sync: cgr.dev/ORGANIZATION/openstack-designate-oshelm-fips:2026.1
    designate_api: cgr.dev/ORGANIZATION/openstack-designate-oshelm-fips:2026.1
    designate_central: cgr.dev/ORGANIZATION/openstack-designate-oshelm-fips:2026.1
    designate_mdns: cgr.dev/ORGANIZATION/openstack-designate-oshelm-fips:2026.1
    designate_worker: cgr.dev/ORGANIZATION/openstack-designate-oshelm-fips:2026.1
    designate_producer: cgr.dev/ORGANIZATION/openstack-designate-oshelm-fips:2026.1
    designate_sink: cgr.dev/ORGANIZATION/openstack-designate-oshelm-fips:2026.1
    designate_service_cleaner: cgr.dev/ORGANIZATION/openstack-designate-oshelm-fips: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 designate openstack-helm/designate --namespace openstack --values values.yaml

The chart's database, keystone, and bootstrap jobs use the openstack-client image, and its dependency-check and RabbitMQ init containers use their own images; all are unaffected.

Configuration

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

Documentation and Resources

• OpenStack Designate 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.