thockingoog

14 ms·

91.
by thockingoog 10y ago
The CoreOS team and technologies have been critical to getting Kubernetes going. Thanks, Brandon.
92.
by thockingoog 10y ago
You folks don't know how much it means to us to hear that people are finding success with Kubernetes. Thanks for using it. We'll try to keep pushing the envelope.
93.
by thockingoog 11y ago
You're still making my point. Using something like MySQL on Borg is not trivial.
94.
by thockingoog 11y ago
Some internal projects started evaluating Kubernetes well before 1.0. We don;t talk about them much because they are, well, internal. This is NOT in competition with Borg, though. Not yet.
95.
by thockingoog 11y ago
The question had an implied "... in Borg" suffix. The point was to demonstrate that Borg does not have "legacy" affordances like durable storage (well, not in the same way as MySQL would need).
96.
by thockingoog 11y ago
Hmm, what was misleading? That certainly was never the intent. A decade or history lead to the knowledge that a particular style of monitoring was needed. That knowledge lead to cAdvisor. Is it perfect, of course not, but it fills a need
97.
by thockingoog 11y ago
I can not reply to your last comment, but "port 80 request denied". And where do you store your MySQL data? The point being nothing is impossible, just prohibitively hard.
98.
by thockingoog 11y ago
We have multi-scheduler support in v1.2 :)
99.
by thockingoog 11y ago
The code is literally millions of LoC, all of which needs to be audited for stuff we can't release for whatever reasons. All that code is built upon layer after layer of Google internal stuff. Open-sourcing Borg means open-sourcing C
100.
by thockingoog 11y ago
Wonderful rebuttal. Proof? There are some successful projects, but that is not a community. There are some libs, but that is not a community. The Go community is vibrant and growing. Go is an easy language to learn (and I say that as so
101.
by thockingoog 11y ago
How would you run Apache + PHP + MySQL on Borg? Hint: you can't. Not without HUGE difficulty, anyway. Nobody does it. Part of Kubernetes "meet people where they are" mindset is that we simply can not ask people to rewrite
102.
by thockingoog 11y ago
As for "no other batteries that fit it" - I am confused. We do run on AWS, OpenStack, and other cloud providers, as well as on bare metal. It's not like nobody is using this thing. In fact, just a finger in the wind, I&#x2
103.
by thockingoog 11y ago
"Powerful scheduling" is such a tiny piece of what Kubernetes does, it's funny. Yeah, Borg's scheduler is faster and more scalable and has more features. It also has 12 years of optimizations under its belt. I have 10
104.
by thockingoog 11y ago
As cited above, we simply CAN'T opensource Borg. It's enormous, and it is deeply, DEEPLY entangled with millions of LoC of Google code. Nobody could untangle that. And even if we DID untangle it, it's alien technology. It
105.
by thockingoog 11y ago
Nobody on the Kubernetes project ever claimed that it was an internal project gone public. It was absolutely, 100% designed to be open-sourced as a derivative of Borg and Omega. There's not sleight of hand here. That said, we had been
106.
by thockingoog 11y ago
This is true. Early cgroups came primarily from Google. Namespaces did not. We have also been very involved in development of various cgroup controllers, and very vocal about what changes will make our style of isolation (which is suddenl
107.
by thockingoog 11y ago
Hi Chuck! At risk of speaking for Bryan, I think the difference between a NetApp and a unikernel-in-a-hypervisor is the sharedness of it. Without taking a position on Bryan's article (it's always entertaining to read his thoughts
108.
by thockingoog 11y ago
I could rant for hours about all the things GitHub doesn't do (or does wrong) for "real" software development. +1 from the Kubernetes project
109.
by thockingoog 11y ago
First, there are a LOT of people working on Kubernetes right now. Second, of course it will be asymptotic for a long time. But keep in mind that we don't want or need everything that Borg has, and Borg does not have everything that Ku
110.
by thockingoog 11y ago
While it is true that Borg is 10 years ahead of Kubernetes, we have the benefit of knowing where Borg arrived rather than following the same winding course.
111.
by thockingoog 11y ago
What key bits do you think are missing from Kubernetes? I'm sorry you seem to have had a bad experience with GCE, but please know that Kubernetes runs on several other clouds, too, with no crippleware or anything. It is 100% open.
112.
by thockingoog 11y ago
I haven't seen any examples of apps that broke because of the kubernetes network model - can you point me at them? I want to understand.
113.
by thockingoog 11y ago
Kubernetes supports 100 nodes with ease, and we expect to handle much more than that very quickly. We just had to pick some target to start with.
114.
by thockingoog 12y ago
Yes, in theory, but we have not really tackled IPv6 yet. Soon :)
115.
by thockingoog 12y ago
I'll concur that the GitHub code-review UX is atrocious. Having used a small number of other code review tools, I can't fathom how GitHub's tooling is so brain-damaged. It does a few cute and clever things, but I totally a
116.
by thockingoog 12y ago
This was a key principle of LMCTFY, too, FWIW.
117.
by thockingoog 12y ago
There's another gotcha in super-small images - things like "docker exec" will not work because there's nothing to exec. SSH-to-container becomes impossible. I think there's got to be a middle-ground - small (maybe
118.
by thockingoog 12y ago
Static binaries are congruent to containers, in a way. Both bundle an app and dependencies together. There are advantages and disadvantages to both approaches, but Docker-style containers are more elegant in some ways.
119.
by thockingoog 12y ago
We've been talking about containers for years. I presented some of our problems with them back in 2011, and I know we've been talking about it before that. :)
120.
by thockingoog 12y ago
Kubernetes is not intrinsically tied to GCE. It's open, and can be made to work on any cloud platform.

More ›