OpenShift Network Operations: Difference between revisions
Jump to navigation
Jump to search
Line 17: | Line 17: | ||
=Pod Network Management= | =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== | ==Joining Projects== | ||
Line 29: | Line 29: | ||
==Making Projects Global== | ==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 [[OpenShift_Concepts#Global_Project|global]] projects. |
Revision as of 22:12, 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
oc get namespaces
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.