Kubernetes NMState Operator

ose-kubernetes-nmstate-operator-bundle-container-v4.17.0.202510142111.p2.g9c27e51.assembly.stream.el9-1

v4.17.0.202510142111.p2.g9c27e51.assembly.stream.el9-1

v4.17

7b2bf46a7fb2e9535dec15aa4078ddd05e8e0c874410882cab1f9bf51eda4edd

v4.17.0.202510142111.p2.g9c27e51.assembly.stream.el9

Overview

Description

# Kubernetes-NMState Declarative node network configuration driven through Kubernetes API ## How it works Kubernetes-NMState uses [NMState](https://nmstate.io) to perform state driven network configuration on cluster nodes and to report back their current state. Both the configuration and reporting is controlled vis Kubernetes objects. ```yaml apiVersion: nmstate.io/v1beta1 kind: NodeNetworkConfigurationPolicy metadata: name: br1-eth0 spec: desiredState: interfaces: - name: br1 type: linux-bridge state: up ipv4: dhcp: true enabled: true bridge: port: - name: eth0 ``` The only external dependency is NetworkManager running on nodes.

Products using this container

Kubernetes NMState is a declaritive means of configuring NetworkManager.

Containerized application

Security

Packages

Containerfile

Get this image

Terms & conditionsBefore downloading or using this Container, you must agree to the Red Hat subscription agreement located at redhat.com/licenses. If you do not agree with these terms, do not download or use the Container. If you have an existing Red Hat Enterprise Agreement (or other negotiated agreement with Red Hat) with terms that govern subscription services associated with Containers, then your existing agreement will control.

Using registry tokens

RegistryCopy to Clipboard

RepositoryCopy to Clipboard

Image DigestCopy to Clipboard

Use the following instructions to get images from a Red Hat container registry using registry service account tokens. You will need to create a registry service account to use prior to completing any of the following tasks.

Using OpenShift secrets

First, you will need to add a reference to the appropriate secret and repository to your Kubernetes pod configuration via an imagePullSecrets field.

Copy to Clipboard

Then, use the following from the command line or from the OpenShift Dashboard GUI interface.

Copy to Clipboard

Using podman login

Use the following command(s) from a system with podman installed

Copy to Clipboard

Using docker login

Use the following command(s) from a system with docker service installed and running

Copy to Clipboard

RegistryCopy to Clipboard

RepositoryCopy to Clipboard

Image DigestCopy to Clipboard

Use the following instructions to get images from a Red Hat container registry using your Red Hat login.

Using OpenShift

For best practices, it is recommended to use registry tokens when pulling content for OpenShift deployments.

Using podman login

Use the following command(s) from a system with podman installed

Copy to Clipboard

Using docker login

Use the following command(s) from a system with docker service installed and running

Copy to Clipboard

Get the source

RegistryCopy to Clipboard

RepositoryCopy to Clipboard

Image DigestCopy to Clipboard

Getting source containers

Source code is available for all Red Hat UBI-based images in the form of downloadable containers. Here are a few things you should know about Red Hat source containers.

Although they are packaged as containers, source containers cannot be run. So instead of using podman pull to get them to your system, use the skopeo command.
Source containers are named based on the binary containers they represent. So, for example, to get the source container for a particular standard RHEL UBI 8 container (registry.access.redhat.com/ubi8/ubi8.1-397) you simply append -source to get the source code container for that image (registry.access.redhat.com/ubi8/ubi8.1-397-source).
The skopeo command is recommended for getting source containers. With skopeo, you copy a source container to a directory on your local system for you to examine.
Once a source container is copied to a local directory, you can use a combination of tar,gzip, and rpm commands to work with that content.

Step one

Use skopeo to copy the source image to a local directory

Copy to Clipboard

Step two

Inspect the image

Copy to Clipboard

Step three

Untar the contents

Copy to Clipboard

Step four

Begin examining and using the content.

Description

Getting source containers

Source code is available for all Red Hat UBI-based images in the form of downloadable containers. Here are a few things you should know about Red Hat source containers.

Although they are packaged as containers, source containers cannot be run. So instead of using podman pull to get them to your system, use the skopeo command.

Source containers are named based on the binary containers they represent. So, for example, to get the source container for a particular standard RHEL UBI 8 container (registry.access.redhat.com/ubi8/ubi8.1-397) you simply append -source to get the source code container for that image (registry.access.redhat.com/ubi8/ubi8.1-397-source).

The skopeo command is recommended for getting source containers. With skopeo, you copy a source container to a directory on your local system for you to examine.

Once a source container is copied to a local directory, you can use a combination of tar,gzip, and rpm commands to work with that content.

Kubernetes NMState Operator

Description

Products using this container