DirectorySecurity AdvisoriesPricing
Sign in
Directory
openstack-neutron-oshelm logo

openstack-neutron-oshelm

packaged by Chainguard

Last changed
Request a free trial

Contact our team to test out this image for free. Please also indicate any other images you would like to evaluate.

Tags
Overview
Comparison
Provenance
Specifications
SBOM
Vulnerabilities
Advisories

Chainguard Container for openstack-neutron-oshelm

Minimal OpenStack Networking (Neutron) image compatible with the upstream openstack-helm neutron 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-neutron-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 Networking (Neutron) image for openstack-helm, compatible with the upstream airshipit/neutron image the neutron chart targets by default.

One image serves every neutron pod the chart deploys: the API server (under uwsgi), the RPC server, the database job, and the privileged Open vSwitch, DHCP, L3 and metadata agents, as well as the OVN, SR-IOV, BGP dynamic routing and bare metal agents and the network namespace cleanup 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 neutron-*, uwsgi and python.

  • The neutron account is uid/gid 42424 with its home at /var/lib/neutron, and the image runs as that user by default (upstream sets no User), matching the chart's runAsUser. /etc/neutron, /var/lib/neutron, /var/log/neutron and /var/cache/neutron are owned by it, as upstream.
  • iptables follows the host's backend (nft or legacy) through iptables-wrappers, so the agents' rules land where kubelet's do.
  • sudo is included so the agents can escalate through the chart's neutron-rootwrap sudoers entry.
  • The tools the agents run are included: Open vSwitch, dnsmasq, haproxy, keepalived, radvd, iproute2, iptables, ipset and conntrack.
  • The VPNaaS, dynamic routing, FWaaS, SFC, tap-as-a-service and networking-baremetal plugins are installed. VPNaaS uses Libreswan: set vpn_device_driver to the Libreswan driver (OvnLibreSwanDriver for OVN), since the chart's default strongSwan driver is not supported.

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

Getting Started

Point every neutron image slot of the chart at this image. Starting from upstream's values_overrides/neutron/2026.1-ubuntu_noble.yaml, a values.yaml looks like this:

images:
  tags:
    neutron_db_sync: cgr.dev/ORGANIZATION/openstack-neutron-oshelm:2026.1
    neutron_dhcp: cgr.dev/ORGANIZATION/openstack-neutron-oshelm:2026.1
    neutron_l3: cgr.dev/ORGANIZATION/openstack-neutron-oshelm:2026.1
    neutron_metadata: cgr.dev/ORGANIZATION/openstack-neutron-oshelm:2026.1
    neutron_netns_cleanup_cron: cgr.dev/ORGANIZATION/openstack-neutron-oshelm:2026.1
    neutron_openvswitch_agent: cgr.dev/ORGANIZATION/openstack-neutron-oshelm:2026.1
    neutron_ovn_agent: cgr.dev/ORGANIZATION/openstack-neutron-oshelm:2026.1
    neutron_ovn_maintenance_worker: cgr.dev/ORGANIZATION/openstack-neutron-oshelm:2026.1
    neutron_ovn_metadata: cgr.dev/ORGANIZATION/openstack-neutron-oshelm:2026.1
    neutron_periodic_worker: cgr.dev/ORGANIZATION/openstack-neutron-oshelm:2026.1
    neutron_rpc_server: cgr.dev/ORGANIZATION/openstack-neutron-oshelm:2026.1
    neutron_server: cgr.dev/ORGANIZATION/openstack-neutron-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 neutron openstack-helm/neutron --namespace openstack --values values.yaml

The chart's other image slots (the bootstrap, database and keystone jobs) use the openstack-client image and are unaffected.

Configuration

Configuration comes from the chart, which renders neutron.conf, the ML2 and agent configuration files and the rootwrap filters, and mounts them under /etc/neutron/. See the openstack-helm neutron chart and the upstream neutron configuration reference for the full set of options.

Documentation and Resources

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:

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.

Licenses

Chainguard's container images contain software packages that are direct or transitive dependencies. The following licenses were found in the "latest" tag of this image:

  • ( GPL-2.0-or-later

  • Apache-2.0

  • Artistic-1.0-Perl

  • BSD-1-Clause

  • BSD-2-Clause

  • BSD-2-Clause-NetBSD

  • BSD-3-Clause

For a complete list of licenses, please refer to this Image's SBOM.

Software license agreement

Compliance

Chainguard Containers are SLSA Level 3 compliant with detailed metadata and documentation about how it was built. We generate build provenance and a Software Bill of Materials (SBOM) for each release, with complete visibility into the software supply chain.

SLSA compliance at Chainguard

This image helps reduce time and effort in establishing PCI DSS 4.0 compliance with low-to-no CVEs.

PCI DSS at Chainguard

Category
Application

The trusted source for open source

Talk to an expert
PrivacyTerms

Product

Chainguard ContainersChainguard LibrariesChainguard VMsChainguard OS PackagesChainguard ActionsChainguard Agent SkillsIntegrationsPricing
© 2026 Chainguard, Inc. All Rights Reserved.
Chainguard® and the Chainguard logo are registered trademarks of Chainguard, Inc. in the United States and/or other countries.
The other respective trademarks mentioned on this page are owned by the respective companies and use of them does not imply any affiliation or endorsement.