davidopp_

9 ms·

1.
by davidopp_ 9y ago
Kubernetes was not designed with the intention that it would be a Mesos framework. But I think it's very cool that people figured out how to make it work as one! From pre-1.0, Kubernetes did resource allocation for CPU and memory via i
2.
by davidopp_ 9y ago
> initially Kubernetes was supposed to be just a Mesos framework... This is not correct. There is a community-owned project that allows Kubernetes to run on Mesos, but it came after standalone Kubernetes. Disclosure: I work on Kubernetes
3.
by davidopp_ 9y ago
Kubernetes runs on GCP, AWS, and Azure, and in various on-prem configurations (including on OpenStack). Disclosure: I work on Kubernetes at Google.
4.
by davidopp_ 9y ago
What's described in that doc is even easier today thanks to Operators ( https://coreos.com/operators ), which, to quote the description page, are "application-specific controller[s] that extend[s] the Kubernetes API
5.
by davidopp_ 9y ago
That idea was proposed here: https://github.com/kubernetes/features/issues/246 ; there's a pretty thorough design doc linked to from the issue. The decision was made not to add it to the system for now (
6.
by davidopp_ 11y ago
https://coreos.com/kubernetes/docs/latest/getting-started.ht... Also http://kubernetes.io/v1.1/docs/getting-started-guides/coreos...
7.
by davidopp_ 11y ago
> I can't remember which issue this was on, but it seemed like there was some discussion on their GitHub project about making pluggable secrets backends (HashiCorp's Vault was mentioned). https://github.com/kube
8.
by davidopp_ 11y ago
All of those scheduling policies are also available in native Kubernetes. The Kubernetes version of that documentation is here: https://github.com/kubernetes/kubernetes/blob/master/docs/de...