On Sunday, October 23, 2016, Yaroslav Molochko <[email protected]> wrote:
> Thank you for your time and valuable suggestions, please find my comments > below: > > On Oct 23, 2016, at 3:37 PM, Rodrigo Campos <[email protected] > <javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote: > > But, to have a solution today, what you say makes sense. But I'm not sure > how > you will communicate between the IN and OUT pods if they are different > pods and > you need unix sockets and it is SO sensible to performance. > > > I was thinking of shared folder from host machine, we could make dedicated > volume for that shared folder, which can be even in tmpfs just to avoid > inodes crawling attack vector. > > I would consider doing: 1 pod that has several containers, several IN > containers > that each reserve the CPU usage you want and one OUT container (that also > reserves the mem usage you want). All in one pod. > > This way, you can communicate via unix sockets using an emptyDir volume or > HostPath if that is more performant. Also, the OUT container may need to > use > hostNetwork to do the outgoing IP thing you need. > > And if a logical host consists of several IN and one OUT instances, then > you > really want them all in the same pod. That what a pod tries to abstract, > really. > > > Thanks for the suggestions, what bothers me though, this may lead to extra > work on building up dedicated pod configurations (means extra replicaset) > for each type of node we have. During years of evolution, we’ve got plenty > of system types, from 1Core 1GB RAM to 32core 64GB of RAM and everything in > the middle :) This is around dozen of configurations so it is doable in > general, but I would love to abstract HW level completely. > Why would it lead to that? You can't put more than one instance of an app in one node? Is this because of the IP address of each node? Thanks a lot, Rodrigo -- You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and Q&A" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/kubernetes-users. For more options, visit https://groups.google.com/d/optout.
