thockingoog

11 ms·

61.
by thockingoog 10y ago
This is why it's important to clarify what "Docker" means in context. Kube and OpenShift DO use Docker (the lower-level infrastructure parts of it, but not the higher-level platformy parts of it). That represents the evoluti
62.
by thockingoog 10y ago
Replying to myself: The fact that someone builds tooling on top of your offering is not an indictment of your product. It simply means people are using it. Be worried when people STOP trying to wrap your stuff with their own opinions.
63.
by thockingoog 10y ago
My point was that we have enterprises who are using it and helping to shape it. There are parts that are simply under-developed and there are parts that are downright embarrassing, no denial. I do expect that many of the docs/articles
64.
by thockingoog 10y ago
I would never deny that there's a lot of work to do, but let's be clear: Kubernetes' security model is evolving in concert with a large number of high-profile users' demands. Designing security in the absence of real cus
65.
by thockingoog 10y ago
> If enough of our customers ask us, maybe we'll eventually integrate kubernetes as an optional component I have agitated for a long time that it's silly to be competing at the layer of orchestration - it's not a revenue-p
66.
by thockingoog 10y ago
I think this distinction is important for people to internalize. Docker heard the userbase that there needed to be a distinction between the "bottom half" and the "top half" of the Docker stack. Giving away the Docker n
67.
by thockingoog 10y ago
MiniKube as a local env is getting great feedback filling this niche.
68.
by thockingoog 10y ago
> Nobody ever deploys kub alone in production That doesn't gel with any reality I know of, sorry. Lots of people use higher level platforms, or develop bespoke tooling, to be sure, but that's going to be true forever, for ever
69.
by thockingoog 10y ago
> Kubernetes is a component (like containerd or swarmkit) That's a bit of stretch. Everything that people use to build something bigger is a "component", but that doesn't make it not a platform. Kubernetes is absolut
70.
by thockingoog 10y ago
I don't think this is 100% fair. Docker (the infrastructure)is relied on by SO MANY people and projects that I don't see it going away, even if Docker (the company) shut their doors tomorrow. Now, it's not clear to us in the
71.
by thockingoog 10y ago
You can either use local disk (thereby tying to a node) or network disk (fully supported, but apparently not good enough in any number of dimensions) or local+replication which kube does NOT currently solve cleanly. The model I want to see
72.
by thockingoog 10y ago
It "WILL NOT WORK" because we need to use additional information for scheduling against a PV that uses local data. That work isn't done because we are still trying to find the right balance of API for local vs durable. It HA
73.
by thockingoog 10y ago
I get that local storage is good for perf, and everyone has some, but you HAVE to understand how disastrously bad it is for availability (unless you do replication yourself, a la Cassandra). That said, we hear you, we're contemplating
74.
by thockingoog 10y ago
+1 Death to `pause` (and it's largely my fault in the first place)
75.
by thockingoog 10y ago
IF this announcement is all it seems, and I am expecting CoreOS folks to find any real trouble spots, this makes the various options at the lower-part of the stack much more similar.
76.
by thockingoog 10y ago
yeah, this is key. It looks like JUST enough to be useful without the rest of the Docker engine.
77.
by thockingoog 10y ago
To my eyes, this signals that Docker hears the complaints from systems like Kubernetes that want to build on top of docker, but don't want all the Docker platform stuff. Layering matters, and Docker seems to be offering a solution that
78.
by thockingoog 10y ago
LOL. Borg is 13 years old, and has THOUSANDS of person-years of work in it. Kubernetes is less than 3 years old. Kubernetes is great, but Borg is a custom-built, totally proprietary system which is fully integrated in the Google ecosyste
79.
by thockingoog 10y ago
This was all in the Seattle office. From the Mountain View office, some of the Borg team had been muttering about "something something Borg as a service", but we really didn't know the first thing about cloud products. When
80.
by thockingoog 10y ago
> The focus on diversifying away from Docker is very recent, > and is the direct result of the competitive tension I think you miss a reason at least equally as important, if not more: There are a lot of people who want to do non-co
81.
by thockingoog 10y ago
Does it support multiple SANs on a single cert? I want to streamline things like vanity domain redirections, where every domain I add requires me to refresh the cert.
82.
by thockingoog 10y ago
As someone who has been on the receiving end of Clayton's arguments (and a sometimes-winner :), I vouch. What he says above is really and truly the highest compliment one could pay.
83.
by thockingoog 10y ago
GKE is currently 4 days behind OSS. That's hardly "weeks behind". 1.4.0 is available in GKE right now .
84.
by thockingoog 10y ago
disclosure: Kubernetes engineer > If by google's age and experience, you mean the requirements of the Google Cloud Quite on the contrary. Kubernetes flies in the face of Google's cloud APIs, and has to take advantage of every d
85.
by thockingoog 10y ago
w00t!!!
86.
by thockingoog 10y ago
We do! it's just not a "persistent" volume because, well, it's not persistent...
87.
by thockingoog 10y ago
an LVM device is local, which is not supported as PersistentVolume. :(
88.
by thockingoog 10y ago
It's funny how words can be played. The Kubernetes "master" is a set of 1 or more machines that run the API server and associated control logic. This is exactly what systems like Docker swarm do, but they wrap it in terms
89.
by thockingoog 10y ago
You can't, in general, adjust the size of block devices purely transparently. We don't currently support blockdev resizing. Would love to talk about how to achieve that, though
90.
by thockingoog 10y ago
It was so close, it just missed the boat. It will hopefully be on the next boat.

More ›