to be fair, it is easy of you make lots of assumptions.
-
-
I am 150% with you. It's hard partly because what we have is a lot more powerful, but also because we don't like to make assumptions
2 replies 0 retweets 7 likes -
Replying to @gabrtv
I suggested recently that maybe kube should embed etcd. End all debate about etcd vs consul, remove a box from the diag.
@aronchick2 replies 0 retweets 4 likes -
would this limit HA. Having them separate means scaling apiserver != scaling etcd. Different problems and solutions.
1 reply 0 retweets 2 likes -
happy to explore anything that makes it easier for users!
1 reply 0 retweets 2 likes -
A giant monolith doing orchestration? Not sure that's desirable long term.
1 reply 0 retweets 4 likes -
maybe "built-in" is one operating mode,while "use this etcd cluster" or "use this consul cluster" are others..
2 replies 0 retweets 5 likes -
Embedding etcd makes sense for some use cases, not all. Scaling, resource contention, failure modes, upgrades, ...
3 replies 0 retweets 5 likes -
Replying to @bgrant0607 @tgraf__
whoah, Brian is on Twitter! Guys and Gals, this is a Big Deal. :)
1 reply 0 retweets 3 likes
Replying to @thockin
and this thread forced me to turn off notifications
6:16 PM - 21 Jun 2016
0 replies
0 retweets
1 like
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.