Skip to content

Followup edits to the scaling and performance networking info #4177

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.

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
Feb 22, 2018
Merged
Changes from all commits
Commits
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
15 changes: 8 additions & 7 deletions scaling_performance/network_optimization.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -96,18 +96,19 @@ can also be set to any other CNI-compatible plug-in as well.
{product-title} provides IP address management for both pods and services. The
default values allow for:

- Maximum cluster size of 1024 nodes
- Each of the 1024 nodes has a /23 allocated to it (510 usable IP addresses for pods)
- Provides 65,536 IP addresses for services.
- A maximum cluster size of 1024 nodes
- Each of the 1024 nodes having a /23 allocated to it (510 usable IPs for pods)
- Around 65,536 IP addresses for services

Under most circumstances, these networks cannot be changed after deployment. Thus it is important to plan ahead for growth.
Under most circumstances, these networks cannot be changed after deployment.
So, planning ahead for growth is important.

Restrictions for resizing networks are document here:
Restrictions for resizing networks are document in the
xref:../install_config/configuring_sdn.adoc#configuring-the-pod-network-on-masters[Configuring
SDN documentation].

If you would like to plan for a larger environment, here are some example values to consider adding to the `[OSE3:vars]` section in your
Ansible inventory file:
To plan for a larger environment, the following are suggested values to consider
adding to the `[OSE3:vars]` section in your Ansible inventory file:
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jeremyeder did you intentionally erase the other values for the inventory file as well? Also, is this supposed to happen at install?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Which other values are you referring to @bfallonf ?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.


----
[OSE3:vars]
Expand Down