Skip to content

OSDOCS-17990: clarify HCP CIDR defaults #111349

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

Closed
JoeAldinger wants to merge 1 commit into from
+2 −2
Closed

OSDOCS-17990: clarify HCP CIDR defaults #111349

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
4 changes: 2 additions & 2 deletions modules/hcp-cidr-ranges.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,12 +7,12 @@
= CIDR ranges for {hcp}

[role="_abstract"]
To successfully deploy {hcp} on {product-title}, define the network environment by using specific Classless Inter-Domain Routing (CIDR) subnet ranges.
To deploy {hcp} on {product-title}, configure CIDR subnet ranges that do not overlap with the management cluster CIDR ranges.

The following Classless Inter-Domain Routing (CIDR) subnet ranges are the default settings for {hcp}:

* `v4InternalSubnet`: 100.65.0.0/16 (OVN-Kubernetes)
* `clusterNetwork`: 10.132.0.0/14 (pod network)
* `serviceNetwork`: 172.31.0.0/16

By using one of the default subnet ranges, you can avoid CIDR overlap with the management cluster and avoid connectivity issues. However, you can use other CIDR subnet ranges if they do not overlap with the management cluster.
The default subnet ranges avoid CIDR overlap with the management cluster and reduce the risk of connectivity issues. You can use other CIDR subnet ranges if they do not overlap with the management cluster.