Re:Kubernetes at Box: Microservices at Maximum Velocity
by hosh on Saturday July 23, 2016 @01:52AM
(#12148529)
Fair enough. I'm not familiar with mcrouter or memcache.
Fronting the mcrouter pods with a service and using a node port (http://kubernetes.io/docs/user-guide/services/#type-nodeport) is not workable?
I have considered just writing a quicky daemon that will do just the work of syncing routes without getting a lease (or trying to modify flanneld to do so).
The service in this case is memcache with a bunch of mcrouter pods in front of it to handle failure and cold cache warming. I still need to get traffic to the mcrouter instances and that's where I'm running into the bottleneck.