4 ms·

Absolutely. Running k8s on bare metal requires full-time dedicated staff. Running k8s with GKE, and possibly also Azure Container Service, though I have no dire

by pacala 9y ago

Absolutely. Running k8s on bare metal requires full-time dedicated staff. Running k8s with GKE, and possibly also Azure Container Service, though I have no direct experience, is a one-off half-day effort. What people usually don't realize is that once you're in the cloud, all your services talk TCP. A service in GKE and another one in AWS are just a network hop away. Two considerations are: * Network egress costs, which is currently outrageously high, and serves as a lock-in device of sorts. Depending on actual workloads, it may or maynot make sense for you. * Security. Though there are numerous VPC solutions out there, some of them supported by the cloud providers themselves. Anecdotically, we also run a small RDS database in AWS, though we only need ~100 small queries a day.

bankss 9y ago
Yeah, thanks for sharing your experiences on that. Unfortunately our egress costs would likely be significant. I am honestly anxious to get my employer started on the path to k8s, but until the tooling reduces the hours required to maintain it successfully, Swarm seems like the superior solution if you are locked in on a non-GKE/Azure Container Service provider. I have heard good things about Kops helping setup/enable production-stable orchestration, but they are not ready yet for Digital Ocean either, although I think it is on the list™.
- hosh 9y ago
  Digital Ocean recently announced a partnering with a Kubernetes vendor. You can run managed K8S on DO now.
  - holmb 9y ago
    Do you have a URL for that announcement?
- jacques_chester 9y ago
  Pivotal and Google built Kubo (recently renamed to the less memorable Cloudfoundry Container Runtime[0]) to make the deployment/management/upgrade thing easier. It's built on top of BOSH, which has a relatively long track record in managing stateful, long-lived, distributed systems on top of IaaSes. Disclosure: I work for Pivotal. [0] https://cloudfoundry.org/container-runtime/ https://cloudfoundry.org/container-runtime/

by pacala 9y ago

bankss 9y ago

Yeah, thanks for sharing your experiences on that. Unfortunately our egress costs would likely be significant. I am honestly anxious to get my employer started on the path to k8s, but until the tooling reduces the hours required to maintain it successfully, Swarm seems like the superior solution if you are locked in on a non-GKE/Azure Container Service provider. I have heard good things about Kops helping setup/enable production-stable orchestration, but they are not ready yet for Digital Ocean either, although I think it is on the list™.

hosh 9y ago
Digital Ocean recently announced a partnering with a Kubernetes vendor. You can run managed K8S on DO now.
- holmb 9y ago
  Do you have a URL for that announcement?
jacques_chester 9y ago
Pivotal and Google built Kubo (recently renamed to the less memorable Cloudfoundry Container Runtime[0]) to make the deployment/management/upgrade thing easier. It's built on top of BOSH, which has a relatively long track record in managing stateful, long-lived, distributed systems on top of IaaSes. Disclosure: I work for Pivotal. [0] https://cloudfoundry.org/container-runtime/ https://cloudfoundry.org/container-runtime/