openstack-octavia-oshelm

packaged by Chainguard

Chainguard Container for openstack-octavia-oshelm

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

• The image runs as the octavia account (uid/gid 42424, home /var/lib/octavia) by default, where the upstream image runs as root. This matches the chart's runAsUser for the API, driver agent, and housekeeping. The db-sync job sets none, so it now runs as octavia instead of root. The chart still runs octavia-worker and octavia-health-manager as root, so chart deployments are unaffected.
• One image serves every octavia workload the chart deploys: the octavia-api Deployment (the Load Balancer API under uwsgi, with the octavia-driver-agent sidecar), octavia-worker, octavia-health-manager, octavia-housekeeping, and the db-sync job.
• 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 and octavia-*.
• dhclient is included, so the worker and health manager bring up their o-w0 and o-hm0 management ports the way the chart's start scripts expect.
• The OVN provider driver (ovn-octavia-provider) is included in addition to the default amphora provider. The upstream image does not include it.
• sudo is not included. The upstream image ships it, but the chart does not use it.

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

Getting Started

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

images:
  tags:
    octavia_api: cgr.dev/ORGANIZATION/openstack-octavia-oshelm:2026.1
    octavia_db_sync: cgr.dev/ORGANIZATION/openstack-octavia-oshelm:2026.1
    octavia_driver_agent: cgr.dev/ORGANIZATION/openstack-octavia-oshelm:2026.1
    octavia_worker: cgr.dev/ORGANIZATION/openstack-octavia-oshelm:2026.1
    octavia_housekeeping: cgr.dev/ORGANIZATION/openstack-octavia-oshelm:2026.1
    octavia_health_manager: cgr.dev/ORGANIZATION/openstack-octavia-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 octavia openstack-helm/octavia --namespace openstack --values values.yaml

The chart's other image slots (the database and keystone init jobs, the port lookups, and the Open vSwitch NIC init containers) use the openstack-client and openvswitch images, and the RabbitMQ init job uses the rabbitmq image; they are unaffected.

Prerequisites

The amphora provider needs a running compute kit (keystone, glance, nova, neutron, and placement), an amphora image, a management network, security groups, a flavor, and the amphora certificates before the chart is installed. See the Octavia installation guide and upstream's deploy-octavia.yaml playbook, which prepares all of them.

Configuration

Configuration comes from the chart, which renders octavia.conf and the uwsgi configuration and mounts them, with the amphora certificates, under /etc/octavia/. The amphora image, flavor, network, and security group IDs go into conf.octavia.controller_worker. See the openstack-helm octavia chart and the upstream Octavia configuration reference for the full set of options.

Documentation and Resources

• OpenStack Octavia documentation
• openstack-helm documentation
• openstack-helm octavia chart
• Upstream airshipit/octavia 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.