OpenShift Network Operations: Difference between revisions
Jump to navigation
Jump to search
| Line 27: | Line 27: | ||
pizzaparty-dev 5721085 | pizzaparty-dev 5721085 | ||
playground 7804116 | playground 7804116 | ||
For a specific project name: | |||
oc get netnamespaces <''project-name''> | |||
=Pod Network Management= | =Pod Network Management= | ||
Revision as of 22:35, 17 October 2017
External
Internal
Information about the Network Plugin and the Network Status
oc get clusternetwork
Information about Virtual Networks Assigned to Each Project
Displays the Virtual Network ID (VNID) assigned to each project. It only makes sense for an ovs-multitenant SDN plugin.
oc get netnamespaces
NAME NETID default 0 kube-system 11092823 logging 6208947 management-infra 5562275 openshift 8714409 openshift-infra 13183382 pizzaparty-dev 5721085 playground 7804116
For a specific project name:
oc get netnamespaces <project-name>
Pod Network Management
Isolating Projects
oadm pod-network isolate-projects <project-1> <project-2> ...
As result of executing the command, all pods and services in project-1 and project-2 cannot access any pods and services from other non-global projects in the cluster and vice-versa.
Joining Projects
oadm pod-network join-projects <project-1-name> <project-2-name> ...
Making Projects Global
oadm pod-network make-projects-global <project-1-name> <project-2-name> ...
As result of executing the command, all pods and services in project-1 and project-2 can now access any pods and services from other non-global projects in the cluster and vice-versa, becoming global projects.