Skip to content

Commit 9dbbfe2

Browse files
committed
Supplement the description of IPVS
1 parent ed0a8bc commit 9dbbfe2

File tree

1 file changed

+12
-0
lines changed

1 file changed

+12
-0
lines changed

‎content/en/docs/reference/networking/virtual-ips.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -249,6 +249,18 @@ these are:
249249
waiting for a fast one; if all servers are busy, the algorithm falls back to the `sed`
250250
behavior.
251251

252+
* `mh` (Maglev Hashing): Assigns incoming jobs based on
253+
[Google's Maglev hashing algorithm](https://static.googleusercontent.com/media/research.google.com/en//pubs/archive/44824.pdf),
254+
This scheduler has two flags: `mh-fallback`, which enables fallback to a different
255+
server if the selected server is unavailable, and `mh-port`, which adds the source port number to
256+
the hash computation. When using `mh`, kube-proxy always sets the `mh-port` flag and does not
257+
enable the `mh-fallback` flag.
258+
In proxy-mode=ipvs `mh` will work as source-hashing (`sh`), but with ports.
259+
260+
These scheduling algorithms are configured through the
261+
[`ipvs.scheduler`](/docs/reference/config-api/kube-proxy-config.v1alpha1/#kubeproxy-config-k8s-io-v1alpha1-KubeProxyIPVSConfiguration)
262+
field in the kube-proxy configuration.
263+
252264
{{< note >}}
253265
To run kube-proxy in IPVS mode, you must make IPVS available on
254266
the node before starting kube-proxy.

0 commit comments

Comments
 (0)