In a normal year, the Cloud Foundry project would be hosting its annual European Summit in Dublin this week. But this is 2020, so it’s a virtual event. This year, however, has been a bit of a transformative year for the open-source Platform-as-a-Service project — in more ways than one. With Cloud Foundry executive director Abby Kearns leaving earlier this year, the organizations’ former CTO Chip Childers stepped into the role. Maybe just as importantly, though, the project’s move to Kubernetes as its container orchestration tool of choice — and a renewed focus on the Cloud Foundry developer experience — is now starting to bear fruit.
“In April, I took over the job. I said: ‘Listen, our community has a new North Star. It’s to go take the Cloud Foundry developer experience and get that thing re-platformed onto Kubernetes. No more delay, no more diversity of thought here. It’s time to make the move,’ ” Childers said (with a chuckle). “And here we are. It’s October, we have our ecosystem aligned, we have major project releases that are fulfilling that vision. And we’ve got a community that’s very energized around it continuing the work of progressing this integration with a bunch of cloud-native projects.”
Developers who use Cloud Foundry, Childers argued, love it, but the project now has an opportunity to show a wider range of potential use that it can offer a smoother developer experience on top of virtually any Kubernetes cluster.
One of the projects that is working on making this happen — and which hit its 1.0 release today, is cf-for-k8s. Traditionally, getting up and running with Cloud Foundry was a heavy lift — and something that most companies left to third-party vendors to handle. This new project, which launched in April, allows developers to spin up a relatively light-weight Cloud Foundry distribution on top of a Kubernetes cluster — using projects like Istio and Fluentd, in addition to Kubernetes — and to do so within minutes.
“It comes along with the whole process of reimagining our architecture to pull in other projects a lot more aggressively and allows us to get to feature parity [with the classic VM-focused Cloud Foundry experience] using a lot more complementary open-source projects,” Childers said about the larger role of this project in the overall ecosystem. “That lets our community focus less on building the underlying plumbing and [spend] more time thinking about how to speed up innovation and the developer experience.”
This wouldn’t be open source if there wasn’t another project that does something quite similar — at least at first glance. That’s KubeCF, which hit its 2.5 launch today. This is an open-source distribution of the Cloud Foundry Application Runtime that, as Childers explained, is meant for production use and that was originally meant to provide existing users a bridge onto the Kubernetes bandwagon. Over time, these two projects will likely merge. “Everyone’s collaborating on what this shared vision looks like. They’re just, they’re just two different distributions that handle the different use cases today,” Childers explained.
After six months in his new position, Childers noted that he’s seeing a lot of energy in the community right now. The job is hard, he said, when there’s unhealthy disagreement, but right now, what he’s seeing is “a beautiful harmony of agreement.”