DirectorySecurity AdvisoriesPricing
Sign in
Directory
openstack-openvswitch-oshelm-fips logoFIPS

openstack-openvswitch-oshelm-fips

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-openvswitch-oshelm-fips

FIPS variant of openstack-openvswitch-oshelm, with TLS through 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-openvswitch-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-openvswitch-oshelm-fips is the FIPS variant of openstack-openvswitch-oshelm, a minimal Open vSwitch image for openstack-helm, compatible with the upstream airshipit/openvswitch image the openvswitch chart targets by default.

The image carries the Open vSwitch userspace (ovsdb-server, ovs-vswitchd and the ovs-* tools) and no OpenStack service. The chart runs it as the openvswitch DaemonSet on every network and compute node, where the neutron Open vSwitch agent or OVN drives it. Use it together with the openstack-neutron-oshelm image. For kolla-ansible / kayobe deployments use openvswitch-db-server-kolla and openvswitch-vswitchd-kolla instead; they follow kolla's kolla_start contract rather than openstack-helm's.

Upstream publishes one image (latest-ubuntu_noble) for every OpenStack release. This image is tagged per OpenStack release (e.g. 2026.1 Gazpacho) instead, and each release carries the Open vSwitch stream that the openstack-neutron-<release> packages use, so the agents and the switch agree. Tags of the form <release>-<Open vSwitch version> pin the Open vSwitch version within a release.

  • The image runs as UID 42424 (openvswitch), matching the chart's pod runAsUser. The chart runs its permissions, kernel-module and ovs-vswitchd containers as root, and ovs-vswitchd drops to openvswitch:openvswitch through the chart's conf.ovs_user_name.
  • /etc/openvswitch and /var/lib/openvswitch belong to openvswitch, as upstream.
  • /tini is present for the chart's default pod.tini.enabled: true.
  • ovs-pki, ovs-bugtool, ovs-tcpdump, ovs-pcap, ovs-dpctl-top and the Open vSwitch Python bindings are included, as in upstream's openvswitch-switch and its dependencies. tcpdump itself is not included, as upstream.
  • This image carries a newer Open vSwitch than upstream's Ubuntu package. When switching an existing node, the chart's db-server script converts the database under /run/openvswitch to the newer schema (ovsdb-tool convert).
  • The DPDK variant (upstream's latest-ubuntu_noble-dpdk, used by the chart's dpdk.yaml overrides) is not available.

FIPS Support

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

  • Open vSwitch's TLS connections (OVSDB ssl:/pssl: remotes and managers, OpenFlow controllers) go through the FIPS provider. Cipher suites the provider does not offer, such as ChaCha20-Poly1305, are refused; peers must support an approved suite such as AES-GCM.
  • OVSDB and OpenFlow connections over plain tcp:/unix: remotes are not encrypted; use ssl: remotes for traffic that leaves the node.

Getting Started

Point the openstack-helm openvswitch chart at this image in your values file:

images:
  tags:
    openvswitch_db_server: cgr.dev/ORGANIZATION/openstack-openvswitch-oshelm-fips:2026.1
    openvswitch_vswitchd: cgr.dev/ORGANIZATION/openstack-openvswitch-oshelm-fips:2026.1

Configuration

Configuration comes from the chart, which supplies the db-server and vswitchd startup scripts and stores the switch configuration in the OVSDB database under /run/openvswitch. See the openstack-helm openvswitch chart and the Open vSwitch documentation 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:

  • Apache-2.0

  • BSD-3-Clause

  • GPL-3.0-or-later

  • LGPL-2.1

  • MIT

  • libselinux-1.0

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

This is a FIPS validated image for FedRAMP compliance.

This image is STIG hardened and scanned against the DISA General Purpose Operating System SRG with reports available.

Learn more about STIGsGet started with STIGs

Related images
openstack-openvswitch-oshelm logo

openstack-openvswitch-oshelm


Category
FIPS
STIG

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.