Skip to content
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

Jump to bottom

docs/scalability: set right ipam option #11890

Merged
merged 1 commit into from Jun 5, 2020
Merged

docs/scalability: set right ipam option #11890

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.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
4 changes: 2 additions & 2 deletions Documentation/scalability/scalability.rst
View file
Open in desktop
Expand Up @@ -24,7 +24,7 @@ Setup
--namespace kube-system \\
--set global.endpointHealthChecking.enabled=false \\
--set global.healthChecking.enabled=false \\
--set global.ipam.mode=kubernetes \\
--set config.ipam=kubernetes \\
--set global.k8sServiceHost=<KUBE-APISERVER-LB-IP-ADDRESS> \\
--set global.k8sServicePort=<KUBE-APISERVER-LB-PORT-NUMBER> \\
--set global.prometheus.enabled=true \\
Expand All @@ -38,7 +38,7 @@ Setup
initially on a smaller cluster (3-10 nodes) where it can be used to detect
potential packet loss due to firewall rules or hypervisor settings.

* ``--set global.ipam.mode=kubernetes`` is set to ``"kubernetes"`` since our
* ``--set config.ipam=kubernetes`` is set to ``"kubernetes"`` since our
cloud provider has pod CIDR allocation enabled in ``kube-controller-manager``.

* ``--set global.k8sServiceHost`` and ``--set global.k8sServicePort`` were set
Expand Down