The Kubernetes universe expands with Eirini and CF Containerization
Kubernetes is the right horse to bet on. How do we know? Well, the Kubernetes universe continues to grow with two new offerings from Cloud Foundry, Eirini and CF Containerization. We take a look at these tools and show why Kubernetes is one of the most promising technologies today.
Kubernetes is eating the internet. As one of the fastest growing and most widely adopted tools out there, it’s becoming an essential part of every developer’s toolkit. We’re excited to see how the Kubernetes universe continues to expand in new and interesting directions.
Kubernetes’ growth has been nothing short of meteoric. Their GitHub stats have been impressive, to say the least. Last year, Kubernetes ranked #1 on GitHub’s most discussed repositories, #2 in most reviewed, and, for me, #1 in sailing-related puns. The community growth and buy-in has been unprecedented as well.
That’s why it was fun to see things like the Non-Code Contributor’s Guide and Kubebilder. Both tools lower the barrier to entry for new developers. They also show how Kubernetes is maturing as a technology.
Kubernetes is still young; it’s only 4 years old. We talked to Klaus Ma, a leader for SIG Scheduling, earlier this month. Here’s what he had to say about the recent changes to the project:
There have been several changes over the years, but two changes have been very important, in my opinion.
The first one is that community defined which parts/components are the core of Kubernetes. At the beginning, there were several components in main branch of GitHub, including customized feature from vendors. That made the code base of Kubernetes very large and hard for new contributors to pick up. Currently, Kubernetes defines which components are core, and makes it extendable for vendors to build customized feature for their business like CNI, CSI, CRI.
Another important change is that it’s better organized right now :), there’s sig-architect, the steering committee, sig leaders to guide the technical direction of community, sig-release, PM to track the progress of release, and approvers/reviewers to ensure the quality of code. It’s also easier to let new contributors know where to get help.
What’s new in Kubernetes?
For Eirini, it’s something of a proof of concept. Scheduling is increasingly commoditized, so it’s important to check and see if it’s possible to abstract away from it. (It is!) As a Kubernetes backend, Eirini deploys CF apps to a kube backend by using OCI images and Kube deployments.
However, because Eirini uses its own abstraction library, it’s not actually a Kube backend. In fact, Eirini is a general-use backend for any kind of scheduler. This frees Eirini up, making it possible to schedule to diego, kube, swarm, or whatever scheduler is hip in the next five years.
Eirini also exports staged Cloud Foundry images as Docker images, making it possible to schedule them as needed. Additionally, it decouples buildpack staging and stateless-multitenant-app running with an integrated
cf push flow.
CF Containerization is a little different. While Eirini is open source, CF Containerization is a Cloud Foundry product. It’s designed to package application runtimes as containers instead of VMs, making it possible to deploy them to Kubernetes.
CF Containerization is meant to provide a more complete app lifecycle management platform. Plus, between Eirini and CF Containerization, developers now have a Kubernetes native implementation of Cloud Foundry.
Interested in trying out either? As previously mentioned, Eirini is open source and available on GitHub. Those interested in giving CF Containerization a whirl should opt for the free Cloud Foundry trial!