Kubernetes is to Borg what Frankstein is to the Dali Lama

When I left Google, I was sold on the whole containerized way of running things. Borg is lightyears ahead of every other cluster orchestration project.

Borg doesn't let you do everything. It is designed to run specifically built applications that are containerized. You don't get Docker images with whatever OS stuff you feel like running that day. The OS is always Google's internal OS. You don't get access to whatever binaries you want to install. You don't get go use whatever security you want. Your RPC system is always going to be Stubby (GRPC internal to Google). Your cluster file system is going to be the only one allowed. Period.

Those limits are freeing. You simply need to have resources to run your jobs and deploy them. Your binaries are packaged up and you just need to say what is going to get run.

So naturally, I've used Kubernetes after I left.

Everything about Borg I liked is gone in Kubernentes. It is trying to solve everyone's problem and solves no one's problem.

It is easy to kill your jobs. Its hard to do things like update a single instance. Service meshes???? Really????

Helm? Great, I can kill all my cluster MySQL databases at the flick of my heml config.

Security, what security? Oh, right, the bring my own model that is just crazy hard.

Need it to work with special cloud sidecars (like special identity services)? Well, that's going to be a fun thing.

Upgrades that change the config language so that your jobs won't run anymore. Perfect.....

And btw, love YAML over the Borg config language, NOT!

There are a wealth of monitoring solutions available for engineers and developers to choose from, so how do you select which is most appropriate for you?

Switch between your git profiles easily

Gone are the days of yore when we named are our servers Etsy, Betsy, and Momo, fed them fish, and cleaned their poop. Well, servers were our pets. Fast-forward, to the world of Kubernetes, and each server, is now a UUID. Is it beneficial anymore to continue observing an individual server?

PipeCD provides a unified continuous delivery solution for multiple application kinds on multi-cloud that empowers engineers to deploy faster with more confidence, a GitOps tool that enables doing deployment operations by pull request on Git.

Fully featured and highly configurable SFTP server with optional FTP/S and WebDAV support, written in Go. Several storage backends are supported: local filesystem, encrypted local filesystem, S3 (compatible) Object Storage, Google Cloud Storage, Azure Blob Storage, SFTP.

the authentication and authorization system BuzzFeed developed to provide a secure, single sign-on experience for access to the many internal web apps used by our employees.

Learn what are the different deployment strategies available in Kubernetes and how to use them.