Tim,
This is a hugely appreciated answer. Sorry the question was so generic!
For now, we'll chose separate clusters - understanding the sub-optimal side
effects of that decision. We'll revisit the single-or-multiple cluster question
in a year or so, once we've had a reasonable amount of
EJ,
Thanks for the insight into how you're handling your clusters! That's very
helpful. To your question, we are running in one of the public clouds (AWS).
Since you group clusters by business unit, I have a question about how you
handle your network security. Is it the case that:
(1) All
EJ,
Awesome info and I believe I follow the breakdown. For the record, we're are
nowhere near the scale you're working with - machines or employees :-).
Just one last clarifying question about what you mean by co-locating. I assume
that means all the workloads (pods) within a BU's cluster are
On Sunday, August 13, 2017 at 12:32:24 AM UTC-7, Timo Reimann wrote:
> Somewhat of a middle ground solution might be to create "sub-clusters" using
> taints and tolerations -- that is, have dedicated nodes for dedicated
> application classes or workloads inside a given cluster. It may reduce the
