July 2018
Intermediate to advanced
504 pages
11h 34m
English
While providing a simple to use and mostly adequate mechanism for managing access between projects, the ovs-multitenant plugin lacks the ability to control access at a more granular level. This is where the ovs-networkpolicy plugin steps in—it lets you create custom NetworkPolicy objects that, for example, can apply restrictions to ingress or egress traffic.
In order to migrate from the ovs-multitenant plugin to this one, we have to isolate ordinary projects from each other and allow traffic to and from global projects. Global projects are distinguished by having 0 as their NETID, as seen in the following output:
[root@openshift-master book]# oc get netnamespacesNAME NETID EGRESS IPSdefault 0 []demo-1 9793016 []
Read now
Unlock full access