Kuryr SDN and OKD

Prior to OKD 3.10.119, the ability to configure Kuryr SDN is a Technology Preview feature.

Kuryr (or more specifically Kuryr-Kubernetes) is an SDN solution built using CNI and OpenStack Neutron. Its advantages include being able to use a wide range of Neutron SDN backends and providing inter-connectivity between Kubernetes pods and OpenStack virtual machines (VMs).

Kuryr-Kubernetes and OKD integration is primarily designed for OKD clusters running on OpenStack VMs. Kuryr-Kubernetes components are installed as pods on OKD in the openshift-infra namespace:

  • kuryr-controller - a single service instance, installed on any node. Modeled in OKD as a Deployment.

  • kuryr-cni - container installing and configuring Kuryr as CNI driver on each OKD node. Modeled in OKD as a DaemonSet.


The system running openshift-ansible must be subscribed to the OSP as well as OCP repositories. The OpenStack integration requires a few extra packages. To install the dependencies, run:

$ sudo yum install -y ansible openshift-ansible python2-shade python-dns \
    python2-heatclient python2-octaviaclient python-openstackclient bind-utils

In the Ansible nodes file, specify the following parameters in order to set up Kuryr-Kubernetes as the network plug-in:

 # Enable Kuryr.

 # Set userspace so that there are no iptables remains.

 # Keystone URL.

 # OpenStack domain name of user owning Kuryr resources.

 # OpenStack project name of user owning Kuryr resources.

 # OpenStack project id for Kuryr resources.

 # OpenStack username that will own kuryr resources.

 # Password for that user.

 # Default Neutron security groups' IDs for Kubernetes pods

 # Default Neutron subnet ID for Kubernetes pods.

 # Default OpenStack project ID for Kubernetes resources.

 # Neutron subnet ID for Kubernetes worker node VMs.

 # Default Neutron subnet ID for Kubernetes services.

You must also specify an OpenStack cloud provider as described in the OpenStack configuration documentation.

Prior to the installation, you must also provide a DNS server the OKD nodes will be using for internal name resolution. OpenStack does not provide a node name resolution out of the box. In the following example, is the IP address of the DNS server:


If the DNS server supports remote updates via nsupdate (RFC 2136), the playbooks can populate it automatically, if you add the following configuration:

openshift_openstack_external_nsupdate_keys={private: {"key_secret": "<nsupdate key>", "key_algorithm": "<nsupdate key algorithm>", "key_name": "<nsupdate key name>", "server":}}

Finally, install OKD by running the provision_install.yml playbook. You must specify the dynamic inventory file, inventory.py, and the the path to the Ansible nodes file that you created:

$ ansible-playbook --user openshift -i /usr/share/ansible/openshift-ansible/playbooks/openstack/inventory.py -i ansible-nodes.txt /usr/share/ansible/openshift-ansible/playbooks/openstack/openshift-cluster/provision_install.yml

If you want to do any custom setup on the created nodes before the OKD installation, you can run the provision.yml and install.yml playbooks separately. provision.yml will create the OpenStack resources (nodes, networks, and so on) and install.yml will install OKD.


Once the installation of OKD is finished, you can check if Kuryr pods are deployed successfully:

$ oc -n openshift-infra get pods -o wide
NAME                                READY     STATUS    RESTARTS   AGE       IP              NODE
bootstrap-autoapprover-0            1/1       Running   0          3d       master-0.openshift.example.com
kuryr-cni-ds-66kt2                  2/2       Running   0          3d   infra-node-0.openshift.example.com
kuryr-cni-ds-ggcpz                  2/2       Running   0          3d   master-0.openshift.example.com
kuryr-cni-ds-mhzjt                  2/2       Running   0          3d    app-node-1.openshift.example.com
kuryr-cni-ds-njctb                  2/2       Running   0          3d   app-node-0.openshift.example.com
kuryr-cni-ds-v8hp8                  2/2       Running   0          3d    infra-node-1.openshift.example.com
kuryr-controller-59fc7f478b-qwk4k   1/1       Running   0          3d    infra-node-1.openshift.example.com

kuryr-cni pods should run on every OKD node. Single kuryr-controller instances should run on any of the nodes.

Network policies, namespace isolation and nodeport services are not supported when Kuryr SDN is enabled.