Skip to content

Commit 2cb0bce

Browse files
committed
[OCPBUGS-48096]: HCP proxy docs for mgmt clusters with secondary networks
1 parent 3e88121 commit 2cb0bce

File tree

2 files changed

+11
-0
lines changed

2 files changed

+11
-0
lines changed

hosted_control_planes/hcp-networking.adoc

+2
Original file line numberDiff line numberDiff line change
@@ -18,6 +18,8 @@ include::modules/hcp-proxy-ignition.adoc[leveloffset=+1]
1818
include::modules/hcp-proxy-api.adoc[leveloffset=+1]
1919
//cp workloads that need access to external services and must use the proxy for the management cluster
2020
include::modules/hcp-proxy-mgmt-cluster.adoc[leveloffset=+1]
21+
//proxy configuration when the mgmt cluster has a second network and no default pod network
22+
include::modules/hcp-proxy-addl-network.adoc[leveloffset=+1]
2123

2224
[role="_additional-resources"]
2325
[id="additional-resources_{context}"]

modules/hcp-proxy-addl-network.adoc

+9
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * hosted_control_planes/hcp-networking.adoc
4+
5+
:_mod-docs-content-type: CONCEPT
6+
[id="hcp-proxy-addl-network_{context}"]
7+
= Management cluster with a secondary network and no default pod network
8+
9+
If the management cluster uses a proxy configuration and you are configuring an additional network but you are not attaching the default pod network, you need to add the CIDR of the additional network to the `noProxy` section of the proxy configuration on the management cluster. Otherwise, the Kubernetes API server will route some API requests through the proxy. In the hosted cluster configuration, the CIDR of the additional network is automatically added to the `noProxy` section.

0 commit comments

Comments
 (0)