5 ms·

> complaining that running a blog on Kubernetes is too complex think you're really missing the point here. Why do you think this was included in the post? http

by zemo 7y ago

> complaining that running a blog on Kubernetes is too complex think you're really missing the point here. Why do you think this was included in the post? https://twitter.com/dexhorthy/status/856639005462417409 https://twitter.com/dexhorthy/status/856639005462417409

wayoutthere 7y ago
Oh I get the author’s point, but her use case was “basically a Heroku replacement for easy deployment”. It’s just the wrong use case for Kubernetes and it is well known that deploying to Kubernetes is a bit of a nightmare.
- parasubvert 7y ago
  Except Kubernetes has sucked all the oxygen up in the industry and has had a subset of adherents that trash the alternatives such as Heroku, Cloud Foundry, etc. As such, people do expect it to replace Heroku.
  - root_axis 7y ago
    Anyone who suggests k8s as an alternative to Heroku is wrong. Heroku is a product that manages infrastructure so that the programmer doesn't have to, k8s is a solution for operational engineers that want a code-driven approach to managing their own infrastructure. Suggesting k8s as a replacement for Heroku is like suggesting docker as a replacement for EC2.
    - parasubvert 7y ago
      And yet, they both fight for the same budget. They're absolutely alternatives in that sense. Not necessarily the right tool for the job, but alas, that's not stopped the wave. And eventually, even Heroku will be based on K8s, as they see the writing on the wall. Also note that most adherents view K8s as a replacement (more accurately new API) that replaces EC2. the fundamental unit of computing becomes the Pod, not a VM.
- lbotos 7y ago
  What is the right use case for K8s? And why is "ease of deployment" not something that someone should expect from K8s? I've been sitting on the K8s sidelines for a bit as things iron out, and I've been deploying it on bare metal on a test bed over the last few days with the intention of using it as IaaS for some of my own apps. It seems to be what it's meant to do. Keep my app running on infra following the rules I set.
  - root_axis 7y ago
    The goal isn't "ease of deployment", the goal is "infrastructure as code" so that application infrastructure can be managed in a way similar to application source code (e.g. PRs, blame, code reviews, CI, rollbacks etc). This helps ops people because it allows them to think about infrastructure as abstract resources rather than as a collection of individual machines with specific designations. With k8s, individual machines become a homogenized resource that do not need specialized provisioning depending on the application they will host.
  - cortesoft 7y ago
    > What is the right use case for K8s? It is for making things easy to deploy ONTO the K8s cluster, not for making the cluster itself easy to deploy. The key is only to use it for cases where the deployment of the containers without K8s is more difficult than the deployment of K8s.
- AlphaSite 7y ago
  Isn’t the right answer there Knative or Cloud Foundry? (On top of k8s)
xena 7y ago
I run more than just my blog. I'm also moving discord and IRC bots there too.

by zemo 7y ago

wayoutthere 7y ago

Oh I get the author’s point, but her use case was “basically a Heroku replacement for easy deployment”. It’s just the wrong use case for Kubernetes and it is well known that deploying to Kubernetes is a bit of a nightmare.

parasubvert 7y ago
Except Kubernetes has sucked all the oxygen up in the industry and has had a subset of adherents that trash the alternatives such as Heroku, Cloud Foundry, etc. As such, people do expect it to replace Heroku.
- root_axis 7y ago
  Anyone who suggests k8s as an alternative to Heroku is wrong. Heroku is a product that manages infrastructure so that the programmer doesn't have to, k8s is a solution for operational engineers that want a code-driven approach to managing their own infrastructure. Suggesting k8s as a replacement for Heroku is like suggesting docker as a replacement for EC2.
  - parasubvert 7y ago
    And yet, they both fight for the same budget. They're absolutely alternatives in that sense. Not necessarily the right tool for the job, but alas, that's not stopped the wave. And eventually, even Heroku will be based on K8s, as they see the writing on the wall. Also note that most adherents view K8s as a replacement (more accurately new API) that replaces EC2. the fundamental unit of computing becomes the Pod, not a VM.
lbotos 7y ago
What is the right use case for K8s? And why is "ease of deployment" not something that someone should expect from K8s? I've been sitting on the K8s sidelines for a bit as things iron out, and I've been deploying it on bare metal on a test bed over the last few days with the intention of using it as IaaS for some of my own apps. It seems to be what it's meant to do. Keep my app running on infra following the rules I set.
- root_axis 7y ago
  The goal isn't "ease of deployment", the goal is "infrastructure as code" so that application infrastructure can be managed in a way similar to application source code (e.g. PRs, blame, code reviews, CI, rollbacks etc). This helps ops people because it allows them to think about infrastructure as abstract resources rather than as a collection of individual machines with specific designations. With k8s, individual machines become a homogenized resource that do not need specialized provisioning depending on the application they will host.
- cortesoft 7y ago
  > What is the right use case for K8s? It is for making things easy to deploy ONTO the K8s cluster, not for making the cluster itself easy to deploy. The key is only to use it for cases where the deployment of the containers without K8s is more difficult than the deployment of K8s.
AlphaSite 7y ago
Isn’t the right answer there Knative or Cloud Foundry? (On top of k8s)

xena 7y ago

I run more than just my blog. I'm also moving discord and IRC bots there too.