Re:Kubernetes 1.4: Making it easy to run on Kubernetes anywhere
by pdeva1 on Tuesday September 27, 2016 @01:37AM
(#12587657)
does kubernetes take care of 'connection draining', ie making sure requests in flight are completed before killing traffic to an instance?
Re:Kubernetes 1.4: Making it easy to run on Kubernetes anywhere
by sporkland on Tuesday September 27, 2016 @03:54PM
(#12592555)
Sort of a blend. It will send a sigterm to your process first which should be your signal to start draining and exit when they are done. If you don't finish within a configurable timeout then sigkill is sent.
Re:Kubernetes 1.4: Making it easy to run on Kubernetes anywhere
by x0rg on Tuesday September 27, 2016 @02:22AM
(#12587794)
I was wondering how to make this automated through some sort of pipeline that needs a human to click "go on with the next X % of the rollout and how I would do it with kubectl without too much pain.
Re:Kubernetes 1.4: Making it easy to run on Kubernetes anywhere
by sporkland on Tuesday September 27, 2016 @03:57PM
(#12592575)
We've been doing this with multiple deployments (e.g. 1, half, all) and updating the deployments sequentially when the previous one looked good. (these are all fronted by one service).
Then, you slowly start to spin up your new instances from 1 -> 10 -> 100 (or whatever). The traffic will split automatically because both apps have the same label/selector, and you control the amount by how many instances of each you have.
Disclosure: I work at Google on Kubernetes