whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

add the set of sessionAffinity timeoutseconds (#5474)

Browse Source 
* add the set of sessionAffinity timeoutseconds

* Update service.md
This commit is contained in:
Lion-Wei
2017-09-26 04:07:34 +08:00
committed by Andrew Chen
parent 8db51e099f
commit 657734de6f
1 changed files with 6 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/concepts/services-networking/service.md
+6 -2
View File
@@ -176,7 +176,9 @@ or `Services` or `Pods`.
By default, the choice of backend is round robin. Client-IP based session affinity 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 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").
![Services overview diagram for userspace proxy](/images/docs/services-userspace-overview.svg) ![Services overview diagram for userspace proxy](/images/docs/services-userspace-overview.svg)
@@ -191,7 +193,9 @@ select a backend `Pod`.
By default, the choice of backend is random. Client-IP based session affinity By default, the choice of backend is random. Client-IP based session affinity
can be selected by setting `service.spec.sessionAffinity` to `"ClientIP"` (the 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 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 `Service`'s IP:Port is proxied to an appropriate backend without the clients