openstack-keystone-oshelm-fips

packaged by Chainguard

Chainguard Container for openstack-keystone-oshelm-fips

FIPS variant of openstack-keystone-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-keystone-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-keystone-oshelm-fips is the FIPS variant of openstack-keystone-oshelm, a minimal, distroless drop-in for quay.io/airshipit/keystone, the image the openstack-helm keystone chart targets by default. It follows the same chart contract: it runs as UID 42424, exposes the service virtualenv at /var/lib/openstack with /var/lib/openstack/bin first on PATH, and serves keystone through Apache and mod_wsgi with the chart's stock wsgi.py and Apache configuration. See the openstack-keystone-oshelm documentation for the details of that contract.

The a2enmod / a2dismod helpers are not present; leave conf.software.apache2.a2enmod and a2dismod unset (their chart defaults). /etc/apache2/ports.conf is also absent, because the chart's own vhost sets Listen.

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

FIPS Support

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

• Passwords are hashed with PBKDF2-SHA512 by default (upstream keystone defaults to bcrypt, which is not FIPS-approved). Existing bcrypt hashes keep working and are replaced when the password next changes; recreate application credentials to migrate them.
• With PBKDF2-SHA512, the FIPS provider rejects passwords shorter than 8 characters.
• Keystone-to-Keystone federation (keystone as a SAML identity provider) is not available: keystone signs assertions with RSA-SHA1, which the FIPS provider rejects, and xmlsec1 is not included.
• 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 keystone database user.
• Use TLS for the database connection. A plaintext connection works, but then the database traffic, including credentials, is not protected by the FIPS provider.
• Do not enable oslo.middleware HTTP basic authentication (http_basic_auth_user_file): it verifies bcrypt hashes, and bcrypt is not FIPS-approved.
• Keystone needs the OpenSSL legacy provider, which the image enables by default: dnspython, which keystone imports through eventlet, uses MD5 at import. Do not set CHAINGUARD_LEGACY_ALLOWED=0.

Getting Started

Point the chart's keystone image slots 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 an override file:

cat > keystone-images.yaml <<EOF
endpoints:
  oci_image_registry:
    auth:
      enabled: true
      keystone:
        username: <pull-token-username>
        password: <pull-token-password>
    host_fqdn_override:
      default: cgr.dev
images:
  tags:
    keystone_api: cgr.dev/ORGANIZATION/openstack-keystone-oshelm-fips:2026.1
    keystone_db_sync: cgr.dev/ORGANIZATION/openstack-keystone-oshelm-fips:2026.1
    keystone_fernet_setup: cgr.dev/ORGANIZATION/openstack-keystone-oshelm-fips:2026.1
    keystone_fernet_rotate: cgr.dev/ORGANIZATION/openstack-keystone-oshelm-fips:2026.1
    keystone_credential_setup: cgr.dev/ORGANIZATION/openstack-keystone-oshelm-fips:2026.1
    keystone_credential_rotate: cgr.dev/ORGANIZATION/openstack-keystone-oshelm-fips:2026.1
    keystone_domain_manage: cgr.dev/ORGANIZATION/openstack-keystone-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 keystone openstack-helm/keystone --namespace openstack --values keystone-images.yaml

The remaining slots (bootstrap, db_init, db_drop, ks_user, keystone_credential_cleanup) run openstack-client, not keystone, and are left to the chart.

Configuration

Configuration comes from the chart, which renders keystone.conf and mounts it at /etc/keystone/. See the openstack-helm keystone chart and the upstream keystone configuration reference for the full set of options.

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.