OpenShift Network Plugins: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 12: Line 12:
<font color=red>TODO: unify with the upper layer [[OpenShift_Concepts#SDN.2C_Overlay_Network]]</font>
<font color=red>TODO: unify with the upper layer [[OpenShift_Concepts#SDN.2C_Overlay_Network]]</font>


Pods get IP addresses from [[OpenShift_Concepts#The_Cluster_Network|the cluster network]], and the address allocation and packet routing is provided by a software-defined network (SDN), implemented using [[OpenShift_Concepts#Open_vSwitch|Open vSwitch (OVS)]].
Pods get IP addresses from [[OpenShift_Concepts#The_Cluster_Network|the cluster network]], and the address allocation and packet routing is provided by a software-defined network (SDN), implemented using [[OpenShift_Concepts#Open_vSwitch|Open vSwitch]] (OVS).


=SDN Plug-Ins=
=SDN Plug-Ins=

Revision as of 18:58, 17 October 2017

External

Internal

Overview

TODO: unify with the upper layer OpenShift_Concepts#SDN.2C_Overlay_Network

Pods get IP addresses from the cluster network, and the address allocation and packet routing is provided by a software-defined network (SDN), implemented using Open vSwitch (OVS).

SDN Plug-Ins

subnet

All pods in the cluster can talk to each other, regardless of project (namespace).

Ansible configuration file:

os_sdn_network_plugin_name='redhat/openshift-ovs-subnet'

multitenant

Ansible configuration file:

os_sdn_network_plugin_name='redhat/openshift-ovs-multitenant'

networkpolicy

Operations

Information about the network plugin and network status:

oc get clusternetwork

Information about virtual networks assigned to each project:

oc get namespaces