openstack-designate-oshelm

packaged by Chainguard

Chainguard Container for openstack-designate-oshelm

Minimal OpenStack Designate image compatible with the upstream openstack-helm designate 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-designate-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 Designate image for openstack-helm, compatible with the upstream airshipit/designate image the designate chart targets by default.

• The image runs as the designate account (uid/gid 42424, home /var/lib/designate) by default, where the upstream image runs as root. The chart sets no runAsUser and mounts writable emptyDir volumes at every path its pods write (/etc/designate, /var/cache/designate, and the lock path), so no security-context override is needed.
• On 2026.1, oslo.service rejects an unset workers count. Current chart versions set it for every designate service; with an older chart, set conf.designate.service:<name>.workers: 1 for the central, mdns, producer, sink and worker services, as the upstream image needs too.
• One image serves every designate workload the chart deploys: the designate-api Deployment (the DNS API under uwsgi), designate-central, designate-mdns, designate-worker (including its pool update init container), designate-producer, the db-sync job, and the service-cleaner CronJob, plus designate-sink when manifests.deployment_sink is enabled.
• 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, designate-*, and designate-manage.
• BIND's rndc is included for the bind9 pool backend, as in the upstream image; Wolfi's bind package also ships the named daemon. The chart's default pool uses the PowerDNS backend, which needs only the PowerDNS HTTP API.
• Unlike the upstream image, this image does not include sudo, curl, wget, git, patch, gnupg, host or a system /usr/bin/python3 (use python3 from PATH), nor upstream's /etc/image_info build metadata or /upper-constraints.txt. The chart's designate workloads don't use any of these.

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

Prerequisites

The chart expects MariaDB, RabbitMQ, Memcached, Keystone, and openstack-helm's powerdns chart (for the default pool) running in the openstack namespace (create it first) before you install designate. The worker reads the PowerDNS address from the powerdns Service, so it must exist before the worker pod starts. Install the powerdns chart with manifests.service_api: true, since the default pool creates zones through the PowerDNS API and the Service only exposes that port with it. To have record changes reach PowerDNS before the next SOA refresh, list the pod network in its conf.powerdns.trusted_notification_proxy: designate-worker sends the NOTIFY, and PowerDNS only accepts one from the zone's primary or a trusted proxy.

Getting Started

Write a values.yaml that points every designate image slot of the chart at this image:

images:
  tags:
    designate_db_sync: cgr.dev/ORGANIZATION/openstack-designate-oshelm:2026.1
    designate_api: cgr.dev/ORGANIZATION/openstack-designate-oshelm:2026.1
    designate_central: cgr.dev/ORGANIZATION/openstack-designate-oshelm:2026.1
    designate_mdns: cgr.dev/ORGANIZATION/openstack-designate-oshelm:2026.1
    designate_worker: cgr.dev/ORGANIZATION/openstack-designate-oshelm:2026.1
    designate_producer: cgr.dev/ORGANIZATION/openstack-designate-oshelm:2026.1
    designate_sink: cgr.dev/ORGANIZATION/openstack-designate-oshelm:2026.1
    designate_service_cleaner: cgr.dev/ORGANIZATION/openstack-designate-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 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/. It mounts the pool definition at /tmp/designate_pools.template, and the worker init container renders it into /etc/designate/pools.yaml before running designate-manage pool update. The default pool targets a PowerDNS server deployed by openstack-helm's powerdns chart, which transfers zones from designate-mdns. 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
• openstack-helm designate chart
• Upstream airshipit/designate 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.