Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

We're Leaving Kubernetes

gitpod.io

Post reply on HN
Print view View original

11–20 of 348 posts

Re: We're Leaving Kubernetes

#11

Post by bhouston »

rglover wrote: post #10
bhouston wrote: post #6

I also recently left Kubernetes. It was a huge waste of time and money. I've replaced it with just a series of services on Google Cloud Run and then using Google's Cloud Run Tasks services for longer running tasks. The infrastructure now incredibly understandable and simple and cost effective. Kubernetes cost us >$million in both DevOps time and actually Google Cloud costs unnecessarily, and even worse it cost us tim…

What stack are you deploying?

Stuff like this, just at larger scale:

https://github.com/bhouston/template-typescript-monorepo

This is my living template of best practices.

Re: We're Leaving Kubernetes

#12

Post by datadeft »

The original k8s paper mentioned that the only use case was a low latency and a high latency workflow combination and the resource allocation is based on that. The generic idea is that you can easily move low latency work between nodes and there are no serios repercussions when a high latency job fails.

Based on this information, it is hard to justify to even consider k8s for the problem that gitpod has.

Re: We're Leaving Kubernetes

#13

Post by candiddevmike »

clvx wrote: post #5

I tried doing a dev environment on Kubernetes but the fact you have to be dealing with a set of containers that could change if the base layer changed meant instability in certain cases which threw me off. I ended up with a mix of nix and it's vm build system which is based on qemu. The issue is too tied to NixOS and all services run in the same place which forces you to manage ports and other things. How I wish it c…

> the fact you have to be dealing with a set of containers that could change if the base layer changed meant instability

Can you expand on this? Are you talking about containers you create?

Re: We're Leaving Kubernetes

#14

Post by candiddevmike »

bhouston wrote: post #6

I also recently left Kubernetes. It was a huge waste of time and money. I've replaced it with just a series of services on Google Cloud Run and then using Google's Cloud Run Tasks services for longer running tasks. The infrastructure now incredibly understandable and simple and cost effective. Kubernetes cost us >$million in both DevOps time and actually Google Cloud costs unnecessarily, and even worse it cost us tim…

You know that Cloud Run is effectively a Kubernetes PaaS, right?

Re: We're Leaving Kubernetes

#15

Post by xyst »

I do agree with the points in article that k8s is not a good fit for development environments.

In my opinion, k8s is great for stable and consistent deployment/orchestration of applications. Dev environments by default are in a constant state of flux.

I don’t understand the need for “cloud development environments” though. Isn’t the point of containerized apps is to avoid the need for synchronizing dev envs amongst teams?

Or maybe this product is supposed to decrease onboarding friction?

Re: We're Leaving Kubernetes

#16

Post by richards »

candiddevmike wrote: post #14
bhouston wrote: post #6

I also recently left Kubernetes. It was a huge waste of time and money. I've replaced it with just a series of services on Google Cloud Run and then using Google's Cloud Run Tasks services for longer running tasks. The infrastructure now incredibly understandable and simple and cost effective. Kubernetes cost us >$million in both DevOps time and actually Google Cloud costs unnecessarily, and even worse it cost us tim…

You know that Cloud Run is effectively a Kubernetes PaaS, right?

Google employee here. Not the case. Cloud Run doesn't run on Kubernetes. It supports the Knative interface which is an OSS project for Kubernetes-based serverless. But Cloud Run is a fully managed service that sits directly atop Borg (https://cloud.google.com/run/docs/securing/security).

Re: We're Leaving Kubernetes

#17

Post by bhouston »

candiddevmike wrote: post #14
bhouston wrote: post #6

I also recently left Kubernetes. It was a huge waste of time and money. I've replaced it with just a series of services on Google Cloud Run and then using Google's Cloud Run Tasks services for longer running tasks. The infrastructure now incredibly understandable and simple and cost effective. Kubernetes cost us >$million in both DevOps time and actually Google Cloud costs unnecessarily, and even worse it cost us tim…

You know that Cloud Run is effectively a Kubernetes PaaS, right?

> You know that Cloud Run is a Kubernetes PaaS, right?

Yup. Isn't it Knative Serving or a home grown Google alternative to it? https://knative.dev/docs/serving/

The key is I am not managing Kubernetes and I am not paying for it - it is a fool's errand, and incredibly rarely needed. Who cares what is underneath the simple Cloud Run developer UX? What matters for me is cost, simplicity, speed and understandability. You get that with Cloud Run, and you don't with Kubernetes.

Re: We're Leaving Kubernetes

#18

Post by sofixa »

elcomet wrote: post #7
bhouston wrote: post #6

I also recently left Kubernetes. It was a huge waste of time and money. I've replaced it with just a series of services on Google Cloud Run and then using Google's Cloud Run Tasks services for longer running tasks. The infrastructure now incredibly understandable and simple and cost effective. Kubernetes cost us >$million in both DevOps time and actually Google Cloud costs unnecessarily, and even worse it cost us tim…

Aren't you afraid of being now stuck with GCP?

One of Cloud Run's main advantages is that it's literally just telling it how to run containers. You could run those same containers in OpenFaaS, Lambda, etc relatively easily.

Re: We're Leaving Kubernetes

#19

Post by chanux »

candiddevmike wrote: post #14
bhouston wrote: post #6

I also recently left Kubernetes. It was a huge waste of time and money. I've replaced it with just a series of services on Google Cloud Run and then using Google's Cloud Run Tasks services for longer running tasks. The infrastructure now incredibly understandable and simple and cost effective. Kubernetes cost us >$million in both DevOps time and actually Google Cloud costs unnecessarily, and even worse it cost us tim…

You know that Cloud Run is effectively a Kubernetes PaaS, right?

I guess the point is that for the OP, Kubernetes is now someone else's problem.

Re: We're Leaving Kubernetes

#20

Post by [deleted] »

bhouston wrote: post #6

I also recently left Kubernetes. It was a huge waste of time and money. I've replaced it with just a series of services on Google Cloud Run and then using Google's Cloud Run Tasks services for longer running tasks. The infrastructure now incredibly understandable and simple and cost effective. Kubernetes cost us >$million in both DevOps time and actually Google Cloud costs unnecessarily, and even worse it cost us tim…

[deleted]
Post reply on HN