When to Use Eirini, Quarks or KubeCF for Cloud Foundry + Kubernetes

By: | April 9, 2020
Share

The core objective of the Cloud Foundry community is to deliver the best developer experience we can offer. As Chip Childers has said, the success of open source communities lays in their ability to build bridges — so when Kubernetes became widely popular, the Cloud Foundry community started bringing the two technologies together for the benefit of users. The community is now fully aligned around the mission of bringing the Cloud Foundry developer experience to Kubernetes clusters. 

As a result, the community has created multiple projects that enable developers to use Cloud Foundry with Kubernetes: Eirini, Project Quarks and KubeCF.

This post will help you decide which of these projects best serves your use case for Cloud Foundry and Kubernetes. 

Eirini

Eirini began the community’s journey of pluggable components by offering Cloud Foundry users a choice between Diego (the native scheduler) or Kubernetes.  Eirini’s goal is to ensure that users have the same experience regardless of the scheduler used.

Read more:

  • An informational post by the project anchor, Julian Skupnjak

Project Quarks

Quarks (which includes “CF Operator”) packages CFAR as Docker images, enabling easy deployment to Kubernetes. The resulting containerized CFAR provides an identical developer experience as BOSH-managed Cloud Foundry installations and delivers a familiar operational experience to Kubernetes operators.

Read more:

  • A post by a project member, Mario Manno

KubeCF 

KubeCF is a distribution of CFAR for Kubernetes. It gives developers the productivity offered by Cloud Foundry combined with the ability for platform operators to manage the infrastructure abstraction with Kubernetes tools and APIs.

Read more:

  • A post by a project member, Troy Topnik

Quick Reference Guide

KubeCF combines Eirini and Quarks, and is the easiest way to get the benefits of both Eirini and Quarks.

When to use Eirini: To schedule user apps on Kubernetes.

When to use Quarks: To deploy and manage BOSH releases on Kubernetes.

When to use KubeCF: To distribute Cloud Foundry Application Runtime on top of Kubernetes.

We hope this is useful as you decide which Cloud Foundry project best serves your needs. If you are interested in learning more or would like to provide feedback to the teams, don’t hesitate to hop over to Cloud Foundry slack (#eirini-dev, #quarks-dev, and #kubecf-dev channels).

Swarna Podila Profile Image

Swarna Podila, AUTHOR

Swarna is the Senior Director of Community at the Cloud Foundry Foundation, where she focuses on enriching the Cloud Foundry community.
SEE ALL ARTICLES