Skip to content
Deploy additional networking components on top of your Kubernetes or OpenShift cluster
Branch: master
Clone or download
phoracek Merge pull request #161 from booxter/use-quotes
Added missing quotes for sriov network type and name fields
Latest commit 69cb539 Jun 20, 2019

README.md

Cluster Network Addons Operator

This operator can be used to deploy additional networking components on top of Kubernetes/OpenShift cluster.

On OpenShift 4, it is preferred to use the native OpenShift ClusterNetworkOperator. However, not all features might be supported there.

Configuration

Configuration of desired network addons is done using NetworkAddonsConfig object:

apiVersion: networkaddonsoperator.network.kubevirt.io/v1alpha1
kind: NetworkAddonsConfig
metadata:
  name: cluster
spec:
  multus: {}
  linuxBridge: {}
  sriov: {}
  kubeMacPool: {}
  nmstate: {}
  imagePullPolicy: Always

Multus

The operator allows administrator to deploy multi-network Multus plugin. It is done using multus attribute.

apiVersion: networkaddonsoperator.network.kubevirt.io/v1alpha1
kind: NetworkAddonsConfig
metadata:
  name: cluster
spec:
  multus: {}

Additionally, container image used to deliver this plugin can be set using MULTUS_IMAGE environment variable in operator deployment manifest.

Note: OpenShift 4 is shipped with Cluster Network Operator. OpenShift operator already supports Multus deployment. Therefore, if Multus is requested in our operator using multus attribute, we just make sure that is is not disabled in the OpenShift one.

Linux Bridge

The operator allows administrator to deploy Linux Bridge CNI plugin simply by adding linuxBridge attribute to NetworkAddonsConfig.

apiVersion: networkaddonsoperator.network.kubevirt.io/v1alpha1
kind: NetworkAddonsConfig
metadata:
  name: cluster
spec:
  linuxBridge: {}

Additionally, container image used to deliver this plugin can be set using LINUX_BRIDGE_IMAGE environment variable in operator deployment manifest.

The bridge marker image used to deliver a bridge marker detecting the availability of linux bridges on nodes can be set using the LINUX_BRIDGE_MARKER_IMAGE environment variable in operator deployment manifest.

SR-IOV

The operator allows administrator to deploy SR-IOV device plugin and CNI plugin simply by adding sriov attribute to NetworkAddonsConfig.

apiVersion: networkaddonsoperator.network.kubevirt.io/v1alpha1
kind: NetworkAddonsConfig
metadata:
  name: cluster
spec:
  sriov: {}

By default, device plugin is deployed with a configuration file with no root devices configured, meaning that the plugin won't discover and advertise any SR-IOV capable network devices.

If all nodes in the cluster are homogenous, meaning they have the same root device IDs (or perhaps it's a single node deployment), then you can use SRIOV_ROOT_DEVICES variable to specify appropriate IDs. If they are not, you can deploy with default configuration file and then modify /etc/pcidp/config.json on each node to list corresponding root device IDs. You may need to restart SR-IOV device plugin pods to catch up configuration file changes.

The operator will also deploy a new network attachment definition for SR-IOV network. By default, its name is sriov-network but it can be changed using the SRIOV_NETWORK_NAME environment variable.

One may also want to change the type of the newly created network attachment definition from the default sriov to something else. For example, this is needed for Red Hat's CNV product that is deployed on top of OpenShift that may be already shipped with sriov CNI plugin of different version incompatible with KubeVirt. In this case an admin may want to use different network types for KubeVirt and OpenShift SR-IOV CNI plugins. This can be achieved using the SRIOV_NETWORK_TYPE environment variable.

Additionally, container images used to deliver these plugins can be set using SRIOV_DP_IMAGE and SRIOV_CNI_IMAGE environment variables in operator deployment manifest.

Note: OpenShift 4 is shipped with Cluster Network Operator. OpenShift operator already supports SR-IOV deployment. But it uses older versions of components that are not compatible with KubeVirt SR-IOV feature. Therefore, if SR-IOV is requested in OpenShift cluster network operator, KubeVirt addons operator will return an error.

Kubemacpool

The operator allows administrator to deploy the Kubemacpool. This project allow to allocate mac addresses from a pool to secondary interfaces using Network Plumbing Working Group de-facto standard.

Note: Administrator can specify a requested range, if the range is not requested a random range will be provided. This random range spans from 02:XX:XX:00:00:00 to 02:XX:XX:FF:FF:FF, where 02 makes the address local unicast and XX:XX is a random prefix.

apiVersion: networkaddonsoperator.network.kubevirt.io/v1alpha1
kind: NetworkAddonsConfig
metadata:
  name: cluster
spec:
  kubeMacPool:
   rangeStart: "02:00:00:00:00:00"
   rangeEnd: "FD:FF:FF:FF:FF:FF"

NMState

Note: This feature is experimental. NMState is unstable and its API may change.

The operator allows the administrator to deploy the NMState State Controller as a daemonset across all of one's nodes. This project manages host networking settings in a declarative manner. The networking state is described by a pre-defined schema. Reporting of current state and changes to it (desired state) both conform to the schema. NMState is aimed to satisfy enterprise needs to manage host networking through a northbound declarative API and multi provider support on the southbound. NetworkManager acts as the main (and currently the only) provider supported.

This component can be enabled by adding nmstate section to the NetworkAddonsConfig.

apiVersion: networkaddonsoperator.network.kubevirt.io/v1alpha1
kind: NetworkAddonsConfig
metadata:
  name: cluster
spec:
  nmstate: {}

It communicate with a NetworkManager instance running on the node using D-Bus. Make sure that NetworkManager is installed and running on each node.

yum install NetworkManager
systemctl start NetworkManager

Image Pull Policy

Administrator can specify image pull policy for deployed components. Default is IfNotPresent.

apiVersion: networkaddonsoperator.network.kubevirt.io/v1alpha1
kind: NetworkAddonsConfig
metadata:
  name: cluster
spec:
  imagePullPolicy: Always

Deployment

First install the operator itself:

kubectl apply -f https://raw.githubusercontent.com/kubevirt/cluster-network-addons-operator/master/manifests/cluster-network-addons/0.9.0/namespace.yaml
kubectl apply -f https://raw.githubusercontent.com/kubevirt/cluster-network-addons-operator/master/manifests/cluster-network-addons/0.9.0/network-addons-config.crd.yaml
kubectl apply -f https://raw.githubusercontent.com/kubevirt/cluster-network-addons-operator/master/manifests/cluster-network-addons/0.9.0/operator.yaml

Then you need to create a configuration for the operator example CR:

kubectl apply -f https://raw.githubusercontent.com/kubevirt/cluster-network-addons-operator/master/manifests/cluster-network-addons/0.9.0/network-addons-config-example.cr.yaml

Finally you can wait for the operator to finish deployment:

kubectl wait networkaddonsconfig cluster --for condition=Ready

In case something failed, you can find the error in the NetworkAddonsConfig Status field:

kubectl get networkaddonsconfig cluster -o yaml

For more information about the configuration format check configuring section.

Development

Make sure you have Docker >= 17.05 installed.

# run code validation and unit tests
make check

# perform auto-formatting on the source code (if not done by your IDE)
make fmt

# generate source code for API
make gen-k8s

# build images (uses multi-stage builds and therefore requires Docker >= 17.05)
make docker-build

# or build only a specific image
make docker-build-operator
make docker-build-registry

# bring up a local cluster with Kubernetes
make cluster-up

# bridge up a local cluster with OpenShift 3
export CLUSTER_PROVIDER='os-3.11.0'
make cluster-up

# deploy operator from sources on the cluster
make cluster-sync

# run functional tests on the cluster
make cluster-functest

# access kubernetes API on the cluster
./cluster/kubectl.sh get nodes

# ssh into the cluster's node
./cluster/cli.sh ssh node01

# clean up all resources created by the operator from the cluster
make cluster-clean

# delete the cluster
make cluster-down

Releasing

Steps to create a new release:

  1. Test operator, make sure it deploys all components, exposes failures in NetworkAddonsConfig.Status field as well as progressing status of components and "Ready".
  2. Open a new PR with two commits. The first of them adding new released manifests, the second bumping versions in Makefile. To make this easier, use ./hack/release.sh <previous version> <released version> <future version> <origin remote> <fork remote>
  3. Once the PR is merged, tag its first commit with proper version name x.y.z. This can be done through GitHub UI.
You can’t perform that action at this time.