File tree Expand file tree Collapse file tree 1 file changed +12
-0
lines changed
content/en/docs/reference/networking Expand file tree Collapse file tree 1 file changed +12
-0
lines changed Original file line number Diff line number Diff line change @@ -249,6 +249,18 @@ these are:
249
249
waiting for a fast one; if all servers are busy, the algorithm falls back to the ` sed `
250
250
behavior.
251
251
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
+
252
264
{{< note >}}
253
265
To run kube-proxy in IPVS mode, you must make IPVS available on
254
266
the node before starting kube-proxy.
You can’t perform that action at this time.
0 commit comments