Skip to content

[enterprise-3.9] bug 1656374 added notes for NetworkPolicy feature support #14427

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
sheriff-rh merged 1 commit into from
Apr 11, 2019
Merged

[enterprise-3.9] bug 1656374 added notes for NetworkPolicy feature support #14427

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion admin_guide/managing_networking.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1124,11 +1124,16 @@ network isolation and do not support Kubernetes `NetworkPolicy`. However,

[NOTE]
====
Only the `v1` NetworkPolicy features are available in {product-title}. This
The `v1` NetworkPolicy features are available only in {product-title}. This
means that egress policy types, IPBlock, and combining `podSelector` and
`namespaceSelector` are not available in {product-title}.
====

[NOTE]
====
Do not apply `NetworkPolicy` features on default {product-title} projects, because they can disrupt communication with the cluster.
====

In a cluster
ifdef::openshift-enterprise,openshift-origin[]
xref:../install_config/configuring_sdn.adoc#install-config-configuring-sdn[configured
Expand Down
12 changes: 12 additions & 0 deletions install_config/configuring_sdn.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -242,6 +242,18 @@ $ oc get netnamespace
[[migrating-between-sdn-plugins-networkpolicy]]
=== Migrating from ovs-multitenant to ovs-networkpolicy

[NOTE]
====
The `v1` NetworkPolicy features are available only in {product-title}. This
means that egress policy types, IPBlock, and combining `podSelector` and
`namespaceSelector` are not available in {product-title}.
====

[NOTE]
====
Do not apply `NetworkPolicy` features on default {product-title} projects, because they can disrupt communication with the cluster.
====

In addition to the generic plug-in migration steps above in the xref:migrating-between-sdn-plugins[Migrating between SDN plug-ins section], there is one additional
step when migrating from the *ovs-multitenant* plug-in to the
*ovs-networkpolicy* plug-in; you must ensure that every namespace has a unique
Expand Down