3 ms·
You seem to imply that k8s somehow means having all your hosting and deployment provided by Google, which seems pretty fallacious. Insofar as it gets people to
by jhanschoo 8y ago
You seem to imply that k8s somehow means having all your hosting and deployment provided by Google, which seems pretty fallacious.
Insofar as it gets people to use GCP, it's not necessarily very useful in that regard. Other replies have pointed out that k8s provides a useful abstraction above multiple cloud hosting solution providers. I'd like to add several reasons.
1. Alternative solutions exist. For example, Docker Swarm. It seems to me that Swarm, otoh, is too inflexible for mainstream popularity (?).
2. Alternative hosting solutions exist: why GCP and not, say, AWS?
3. Some companies build on top of the main k8s features and provide their own solutions tied to their own offerings, obviating the use of GCP. For example, rkt and OpenShift.
So even if Google is the dominant interest to the extent that k8s would fail if it stopped its contributions to the project, it is not obvious that Google will be able to capture all the value that comes out of the k8s project (of course, it expects to capture enough of it to make fiscal sense)
- emodendroket 8y agoCould you expound on that a bit? I'm kind of new to the whole container thing and have been making an effort to educate myself, but it's not clear to me what's "wrong" with Docker Swarm that Kubernetes is so much more popular, especially when it seems like everyone is using Kubernetes with Docker already.
- jhanschoo 8y agoAlright, I haven't really delved deep into Swarm and this reply is based on ~15 mins Googling but... 1. Kubernetes since last year has first-class support for role-based access control to elements in the cluster, whereas I can't find access control concepts in Swarm. 2. I have a Kubernetes cluster where the pods simply assume and communicate in HTTP. Within the network, both Kubernetes and Swarm encrypt internal network traffic with its own CA, IIRC. Nevertheless, Kubernetes has an Ingress concept, which allows me to translate external HTTP connections over TLS into the cluster into HTTP connections (and if load is rerouted, re-encrypted with the internal-use certs, of course). This enables my containers to be focused and agnostic about the whole certificate shabang.
- lowmagnet 8y agoAmazon just made EKS (Elastic container for Kubernetes Service) generally available, so yes, other cloud vendors are wise to it.