Get bought, they've decided to back up and leave Kubernetes. Yep, Kubernetes has been the backbone of their cloud infrastructure for years, but now they're saying goodbye. What does that mean for [Music] developers, for those who are new to this?

Kubernetes is like the ultimate project manager for cloud apps. It manages containers, scales things up for you when needed, and ensures reliability for Gitpod, which serves up cloud-based development environments. Gitpod seemed like the perfect tool at first, as Gitpod scaled, cracks started showing. Let's see what went

wrong. Kubernetes has incredible power, but that comes with a lot of complexity. Managing, troubleshooting, and maintaining Kubernetes infrastructure at their scale was slowing things down. Workspaces took longer to boot, costs began piling up, and issues got harder to debug for Gitpod.

It was like driving a sports car through traffic - great potential, but not the right setup. Gitpod realized they needed a tool redesigned specifically for cloud-based development environments, so they are custom building an alternative. Their solution aims to be lighter, faster, and tailored to the workflow of spinning

up cloud dev workspaces quickly and affordably. Instead of using a one-size-fits-all approach, they are moving to something that is just a fit right now. This isn't just a backend shift, it will make a real difference in the experience

of developers. Gitpod's goal is to make cloud environments feel instant. Workspaces that spin up quickly and are always ready, and don't cost a fortune. Imagine logging in, coding immediately, and not thinking twice about the infrastructure behind it. So yeah,

Good Bear is finally leaving Kubernetes and building their own custom solution, and it would be interesting to see what they are building right now.  Because if they revealed or maybe open-sourced their solution, it might be a challenge or maybe in competition to Kubernetes.  I'll see you in the next

This Company ditched Kubernetes and reason is good!

PEXT

쿠버네티스를 포기하기로 한 깃팟의 결정

수년간 Kubernetes에 의존해 온 Gitpod는 사용을 중단하기로 결정합니다.

Kubernetes는 강력하지만 클라우드 앱, 컨테이너 관리 및 확장을 위한 최고의 프로젝트 관리자로 설명됩니다.

Gitpod의 Kubernetes 확장 문제로 인해 작업 공간 부팅 시간이 느려지고 비용이 증가하며 디버깅이 더 어려워졌습니다.

Kubernetes를 포기하고 사용자 정의 솔루션을 구축하는 이유

Kubernetes의 복잡성은 Gitpod의 효율성을 저해하여 맞춤형 솔루션이 필요했습니다.

새로운 솔루션은 빠른 작업 공간 설정에 초점을 맞춘 더 가볍고, 더 빠르고, 더 경제적인 접근 방식을 지향합니다.

개발자를 위한 즉각적이고 비용 효율적인 클라우드 환경을 만드는 것이 목표입니다.

깃팟의 새로운 솔루션의 잠재적 의미

Gitpod의 사용자 정의 솔루션은 오픈 소스화될 경우 잠재적으로 Kubernetes에 도전하거나 경쟁할 수 있습니다.