Skip to content

[OCPBUGS-48096]: HCP proxy docs for mgmt clusters with secondary network #91942

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
merged 1 commit into from
Apr 22, 2025
Merged

[OCPBUGS-48096]: HCP proxy docs for mgmt clusters with secondary network #91942

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
2 changes: 2 additions & 0 deletions hosted_control_planes/hcp-networking.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,8 @@ include::modules/hcp-proxy-ignition.adoc[leveloffset=+1]
include::modules/hcp-proxy-api.adoc[leveloffset=+1]
//cp workloads that need access to external services and must use the proxy for the management cluster
include::modules/hcp-proxy-mgmt-cluster.adoc[leveloffset=+1]
//proxy configuration on the mgmt cluster when the hosted cluster has a secondary network and no default pod network
include::modules/hcp-proxy-addl-network.adoc[leveloffset=+1]

[role="_additional-resources"]
[id="additional-resources_{context}"]
Expand Down
9 changes: 9 additions & 0 deletions modules/hcp-proxy-addl-network.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
// Module included in the following assemblies:
//
// * hosted_control_planes/hcp-networking.adoc

:_mod-docs-content-type: CONCEPT
[id="hcp-proxy-addl-network_{context}"]
= Management cluster that uses a proxy and a hosted cluster with a secondary network and no default pod network

If a management cluster uses a proxy configuration and you are configuring a hosted cluster with a secondary network but are not attaching the default pod network, add the CIDR of the secondary network to the proxy configuration. Specifically, you need to add the CIDR of the secondary network to the `noProxy` section of the proxy configuration for 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 secondary network is automatically added to the `noProxy` section.