Kubernetes backend Eirini hits 1.0 milestone
Eirini is a Kubernetes backend from Cloud Foundry, providing an Orchestrator Provider Interface layer. It allows users to choose Kubernetes as their container scheduler, so they can use the tools that they are already familiar with. Now, Eirini recently hit its version 1.0 release. This important milestone means that Eirini is ready for use and has earned its stability. See what’s new and what’s under the hood.
Reaching version 1.0 is a milestone worthy of celebration. Cloud Foundry’s Project Eirini recently shipped its 1.0 release, marking its core component fully stable and ready to use with CF apps.
Eirini is a Kubernetes backend, providing an Orchestrator Provider Interface and expanding the Kubernetes ecosystem even further. Kubernetes refuses to slow down its momentum and has become the de-facto standard for scheduling.
Take a quick look at what Eirini version 1.0 involves and how it works. This project is currently incubating.
Eirini does the big lifting, which gives your infrastructure a break, bringing
cf push into Kubernetes.
From its README:
Eirini gives you the nice integrated
cf pushflow, with CF Apps mapped directly to kube
StatefulSet. In other words it decouples buildpack staging and stateless-multitenant-app running.
It is a Kubernetes backend for Cloud Foundry and Cloud Foundry apps. Eirini deploys apps to a kube backend using OCI images and Kube deployments.
Kubernetes continues growing in popularity for scheduling containers in the cloud. Generally, it is accepted as the community standard.
Eirini gives this a push and can put containers on servers. It works broadly and can be a generic backend for any scheduler, not just as a Kube backend. Eirini can schedule to any orchestration provider that includes an implementation of the OPI layer for the target platform (such as Diego – Cloud Foundry’s container management system).
Thus, DevOps teams can use whichever scheduler they wish with all the same benefits.
Check out the source code on GitHub.
How it works
How does it all come together? Underneath the hood, Eirini consists of three components.
From its GitHub repo:
Bifrostconverts and transfers cloud controller app specific requests to OPI specific objects and runs them in Kubernetes. It relies on the
bits-serviceto serve OCI images for droplets, and
OPIto abstract the communication with Kube.
OPIor the “Orchestrator Provider Interface” provides a declarative abstraction over multiple schedulers inspired by Diego’s LRP/Task model and Bosh’s CPI concept.
Stagerimplements staging by running Kubernetes/OPI one-off tasks
Project Eirini is written in Golang.
Eirini version 1.0
This milestone means that Eirini is ready for use and has earned its stability. 1.0 also added a few new changes:
- Eirini sends more information from CC to Eirini. Read the issue tracker for more information about what info it sends.
- Fixed a known bug involving cleaning up deleted apps
- Now enforces user-requested disk quotas on app containers in order to support real multi-tenacy
Track progress made to Cloud Foundry Eirini with the Pivotal Tracker and see all the hard work and project history.
Give it a spin
To deploy, follow the instructions on GitHub in the helm release. First, your Kubernetes must meet the requirements set by SCF. Then, you will need helm, Metrics server and the ability to use the bits service private registry in Kubernetes.
If you use IBM Cloud, SUSE, and/or Pivotal, you can also test Eirini as a tech preview.
Why not test it out and give the dev team your feedback!