add the set of sessionAffinity timeoutseconds (#5474)
* add the set of sessionAffinity timeoutseconds * Update service.md
This commit is contained in:
@@ -176,7 +176,9 @@ or `Services` or `Pods`.
|
||||
|
||||
By default, the choice of backend is round robin. Client-IP based session affinity
|
||||
can be selected by setting `service.spec.sessionAffinity` to `"ClientIP"` (the
|
||||
default is `"None"`).
|
||||
default is `"None"`), and you can set the max session sticky time by setting the field
|
||||
`service.spec.sessionAffinityConfig.clientIP.timeoutSeconds` if you have already set
|
||||
`service.spec.sessionAffinity` to `"ClientIP"` (the default is "10800").
|
||||
|
||||

|
||||
|
||||
@@ -191,7 +193,9 @@ select a backend `Pod`.
|
||||
|
||||
By default, the choice of backend is random. Client-IP based session affinity
|
||||
can be selected by setting `service.spec.sessionAffinity` to `"ClientIP"` (the
|
||||
default is `"None"`).
|
||||
default is `"None"`), and you can set the max session sticky time by setting the field
|
||||
`service.spec.sessionAffinityConfig.clientIP.timeoutSeconds` if you have already set
|
||||
`service.spec.sessionAffinity` to `"ClientIP"` (the default is "10800").
|
||||
|
||||
As with the userspace proxy, the net result is that any traffic bound for the
|
||||
`Service`'s IP:Port is proxied to an appropriate backend without the clients
|
||||
|
||||
Reference in New Issue
Block a user