kubernetes/pkg/api/validation
Kubernetes Submit Queue b65f3cc8dd Merge pull request #49850 from m1093782566/service-session-timeout
Automatic merge from submit-queue (batch tested with PRs 49850, 47782, 50595, 50730, 51341)

Paramaterize `stickyMaxAgeMinutes` for service in API

**What this PR does / why we need it**:

Currently I find `stickyMaxAgeMinutes` for a session affinity type service is hard code to 180min. There is a TODO comment, see

https://github.com/kubernetes/kubernetes/blob/master/pkg/proxy/iptables/proxier.go#L205

I think the seesion sticky max time varies from service to service and users may not aware of it since it's hard coded in all proxier.go - iptables, userspace and winuserspace.

Once we parameterize it in API, users can set/get the values for their different services.

Perhaps, we can introduce a new field `api.ClientIPAffinityConfig` in `api.ServiceSpec`.

There is an initial discussion about it in sig-network group. See,

https://groups.google.com/forum/#!topic/kubernetes-sig-network/i-LkeHrjs80

**Which issue this PR fixes**: 

fixes #49831

**Special notes for your reviewer**:

**Release note**:

```release-note
Paramaterize session affinity timeout seconds in service API for Client IP based session affinity.
```
2017-08-25 20:43:30 -07:00
..
BUILD add diff details to pod validation error 2017-08-18 09:01:13 -04:00
doc.go Use Go canonical import paths 2016-07-16 13:48:21 -04:00
events_test.go refactor: move ListOptions references to metav1 2017-01-23 17:52:46 -05:00
events.go refactor: move ListOptions references to metav1 2017-01-23 17:52:46 -05:00
OWNERS Remove myself from a bunch of places 2017-07-20 12:10:46 +02:00
validation_test.go Paramaterize stickyMaxAgeMinutes for service in API 2017-08-25 17:44:47 +08:00
validation.go Merge pull request #49850 from m1093782566/service-session-timeout 2017-08-25 20:43:30 -07:00