Cloud FoundryがKubernetesの進捗状況、新しいCLIを採用

Cloud Foundry FoundationがKubernetesを採用したことで、プラットフォームの新しい扉が開かれたようです。このプラットフォームは、ある時点で、事実上のコンテナオーケストレーションの標準に組み込まれていました。The Cloud Foundry Foundation’s embrace of Kubernetes has seemingly opened up new doors for a platform that at one point was being subsumed by what has become the de facto container orchestration standard. Chip Childers, who recently took over as director of the Cloud Foundry Foundation (CFF) from Abby Kearns, highlighted some of those efforts during a keynote address at this week’s virtual Cloud Foundry North America event. The first is the open source KubeCF runtime that CFF adopted as an incubating project earlier this year. It acts as an open source distribution of the Cloud Foundry Application Runtime (CFAR), which is an app-centric platform designed to support application development lifecycle. KubeCF was developed initially by CFF member SUSE – with initial work dated back to 2015 – and is designed to run on top of Kubernetes and be deployed as a Helm chart. “It’s designed to provide the full Cloud Foundry experience as you know it today on top of Kubernetes, and it accomplishes that by packaging up Cloud Foundry and making sure it can be deployed and managed in a Kubernetes-based environment,” Childers explained. That project also taps CFF’s Project Eirini to use Kubernetes as the underlying container scheduler. Project Eirini has been CFF’s biggest push into the Kubernetes space and allows operators and vendors to use Kubernetes as the underlying container scheduler for the CFAR. It basically provides developers with a “cf push” experience for moving applications into production on top of Kubernetes. The other is the CF for Kubernetes project that was launched in April, and “is fundamentally about re-imagining our architecture,” Childers said. He noted that it builds on the basic functionality of cf push. “Each project team is using it as an opportunity to re-architect, the way that their component of the system works to include more projects from the broader cloud-native open source community, whether it’s inclusion of Fluentd or Prometheus, whether it’s the deeper integration with Istio, whether it’s re-imagining how our own code can exist as [custom resource definitions] within Kubernetes,” Childers said. Both of those projects build on CFF’s increased focus on the Kubernetes ecosystem. Childers previously explained to SDxCentral that Kubernetes remains a hard platform to use in production environments and that it was focused on easing that integration. It targets the Cloud Foundry platform as the simplified, nice, and easy-to-use layer on top of Kubernetes to build “the best enterprise developer experience” and avoid “any of the infrastructure conversation.” Outside of its strict Kubernetes focus, the CFF also announced the general availability release of its Command Line Interface Version 7 (CLI v7). This update to the Cloud Foundry CLI allows for updates to be pushed to applications without having to interrupt the running of those applications; more granular control over the “cf push” process, which is how an application developed in Cloud Foundry is pushed into production by a developer; simplifying the ability to push an application that runs multiple processes; the ability to run additional processes in the same container as an application; and the ability to add metadata to objects. “You get more capabilities, more granular control, but some of the exact same simplicity that past versions of a developer experience had,” Childers explained. “Whether it’s ease of deployment using rolling application patterns or whether it’s running component steps of what the full cf push process actually provides today. … These commands break down the process and the steps that you can run independently and can be run multiple times or repurposed.”