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.

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

Docs: Fix maglev.hashSeed byte size documentation #16690

Merged
merged 1 commit into from
Jul 1, 2021
Merged
Changes from all commits
Commits
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/gettingstarted/kubeproxy-free.rst
Original file line number Diff line number Diff line change
Expand Up @@ -382,7 +382,7 @@ per service. If a higher number of backends are provisioned under this setting,
difference in reassignments on backend changes will increase.

The ``maglev.hashSeed`` option is recommended to be set in order for Cilium to not rely on the
fixed built-in seed. The seed is a base64-encoded 16 byte-random number, and can be
fixed built-in seed. The seed is a base64-encoded 12 byte-random number, and can be
generated once through ``head -c12 /dev/urandom | base64 -w0``, for example. Every Cilium agent
in the cluster must use the same hash seed in order for Maglev to work.

Expand All @@ -392,7 +392,7 @@ given service (with the property of at most 1% difference on backend reassignmen

.. parsed-literal::

SEED=$(head -c16 /dev/urandom | base64 -w0)
SEED=$(head -c12 /dev/urandom | base64 -w0)
helm install cilium |CHART_RELEASE| \\
--namespace kube-system \\
--set kubeProxyReplacement=strict \\
Expand Down