Gitpod, a development platform, has decided to shift its focus to home-grown tools to quit Kubernetes. The standardised, and automated development environment solution plans to transition to a custom-built solution called Flex. Kubernetes often pushed the team to reverse-engineer solutions for unique challenges. Even managed services like GKE and EKS added restrictions that complicated operations. The Gitpod team noted that Kubernetes continues to be a “fine choice” as long as you are running application workloads. In contrast, Google Cloud Run provided a simpler and cost-effective alternative with features like rapid autoscaling, pay-per-use pricing, etc.
The Kubernetes ecosystem is filled with unnecessary add-ons and tools often introduces more complexity than utility, creating a bloated and fragile infrastructure that is harder to maintain. These lead to vendor lock-in, reducing flexibility and driving up costs. Okteto uses customised BuildKit service with file synchronisation to streamline builds and deployments. They ensure development closely mirrors production without compromising feedback loops. Okteto also provides separate Kubernetes clusters for each company and supports multi-cluster setups to address scalability challenges.
The promise of Kubernetes was never about building for developer environments, according to Pablo Chico de Guzman, CTO of Okteto. Similar to what Murli Thirumale from Pure Storage said, Okteto's custom Resource Manager predicts CPU and memory needs by analysing identical services across environments, optimising resource allocation to enhance cluster performance and developer experience. In a discussion on Hacker News, developers from different companies cited several reasons for Kubernetes being cumbersome. The main reasons remain the complex learning curve, maintenance inefficiency, vendor lock-in, overuse, and the mismatch between needs and scale.