Skip to content

Commit be76621

Browse files
committed
OCPBUGS-39198: Added note for esp hardware offload support and IPsec
1 parent faeb00d commit be76621

File tree

1 file changed

+25
-16
lines changed

1 file changed

+25
-16
lines changed

networking/network_security/configuring-ipsec-ovn.adoc

Lines changed: 25 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -6,26 +6,24 @@ include::_attributes/common-attributes.adoc[]
66

77
toc::[]
88

9-
With IPsec enabled, you can encrypt both internal pod-to-pod cluster traffic between nodes and external traffic between pods and IPsec endpoints external to your cluster. All pod-to-pod network traffic between nodes on the OVN-Kubernetes cluster network is encrypted with IPsec in _Transport mode_.
9+
By enabling IPsec, you can encrypt both internal pod-to-pod cluster traffic between nodes and external traffic between pods and IPsec endpoints external to your cluster. All pod-to-pod network traffic between nodes on the OVN-Kubernetes cluster network is encrypted with IPsec in _Transport mode_.
1010

11-
IPsec is disabled by default. It can be enabled either during or after installing the cluster. For information about cluster installation, see xref:../../installing/overview/index.adoc#ocp-installation-overview[{product-title} installation overview].
11+
IPsec is disabled by default. You can enable IPsec either during or after installing the cluster. For information about cluster installation, see xref:../../installing/overview/index.adoc#ocp-installation-overview[{product-title} installation overview].
1212

13-
[IMPORTANT]
14-
====
15-
If your cluster uses link:https://www.redhat.com/en/topics/containers/what-are-hosted-control-planes[{hcp}] for Red Hat {product-title}, IPsec is not supported for IPsec encryption of either pod-to-pod or traffic to external hosts.
16-
====
13+
The following support limitations exist for IPsec on a {product-title} cluster:
1714

18-
[NOTE]
19-
====
20-
IPsec on {ibm-cloud-name} supports only NAT-T. Using ESP is not supported.
21-
====
15+
* On {ibm-cloud-name}, IPsec supports only NAT-T. Encapsulating Security Payload (ESP) is not supported on this platform.
16+
* If your cluster uses link:https://www.redhat.com/en/topics/containers/what-are-hosted-control-planes[{hcp}] for Red{nbsp}Hat {product-title}, IPsec is not supported for IPsec encryption of either pod-to-pod or traffic to external hosts.
17+
* Using ESP hardware offloading on any network interface is not supported if one or more of those interfaces is attached to Open vSwitch (OVS). Enabling IPsec for your cluster triggers the use of IPsec with interfaces attached to OVS. By default, {product-title} disables ESP hardware offloading on any interfaces attached to OVS.
18+
* If you enabled IPsec for network interfaces that are not attached to OVS, a cluster administrator must manually disable ESP hardware offloading on each interface that is not attached to OVS.
2219
23-
Use the procedures in the following documentation to:
20+
The following list outlines key tasks in the IPsec documentation:
2421

25-
* Enable and disable IPSec after cluster installation
26-
* Configure IPsec encryption for traffic between the cluster and external hosts
27-
* Verify that IPsec encrypts traffic between pods on different nodes
22+
* Enable and disable IPsec after cluster installation.
23+
* Configure IPsec encryption for traffic between the cluster and external hosts.
24+
* Verify that IPsec encrypts traffic between pods on different nodes.
2825
26+
// Modes of operation
2927
include::modules/nw-own-ipsec-modes.adoc[leveloffset=+1]
3028

3129
// Uses xrefs, so must be located here
@@ -54,18 +52,29 @@ include::modules/nw-own-ipsec-required-ports.adoc[leveloffset=+1]
5452

5553
For IPsec encryption of pod-to-pod traffic, the following sections describe which specific pod-to-pod traffic is encrypted, what kind of encryption protocol is used, and how X.509 certificates are handled. These sections do not apply to IPsec encryption between the cluster and external hosts, which you must configure manually for your specific external network infrastructure.
5654

55+
// Types of network traffic flows encrypted by pod-to-pod IPsec
5756
include::modules/nw-ovn-ipsec-traffic.adoc[leveloffset=+2]
57+
58+
// Encryption protocol and IPsec mode
5859
include::modules/nw-ovn-ipsec-encryption.adoc[leveloffset=+2]
60+
61+
// Security certificate generation and rotation
5962
include::modules/nw-ovn-ipsec-certificates.adoc[leveloffset=+2]
6063

64+
// IPsec encryption for external traffic
6165
include::modules/nw-ovn-ipsec-external.adoc[leveloffset=+1]
62-
// Enable & then optionally configure IPsec for external hosts
66+
67+
// Enabling IPsec encryption
6368
include::modules/nw-ovn-ipsec-enable.adoc[leveloffset=+1]
69+
70+
// Configuring IPsec encryption for external traffic
6471
include::modules/nw-ovn-ipsec-north-south-enable.adoc[leveloffset=+1]
6572

73+
// Disabling IPsec encryption for an external IPsec endpoint
6674
include::modules/nw-ovn-ipsec-north-south-disable.adoc[leveloffset=+1]
67-
include::modules/nw-ovn-ipsec-disable.adoc[leveloffset=+1]
6875

76+
// Disabling IPsec encryption
77+
include::modules/nw-ovn-ipsec-disable.adoc[leveloffset=+1]
6978

7079
[id="{context}_additional-resources"]
7180
== Additional resources

0 commit comments

Comments
 (0)