Both Cloud Foundry and Kubernetes attract similar, but not exactly the same use cases. In both scenarios, you want to deploy applications and data services.

“So while the Cloud Foundry is more specific and provides you a user experience that is more guiding the application developer, Kubernetes provides more flexibility,” said Julian Fischer, CEO of anynines.

“Cloud Foundry is still a very pleasant way for application developers to deploy applications,” Julian Fischer, anynines.

He said that customers who have invested in Cloud Foundry will continue to use Cloud Foundry because it is still a very pleasant way for application developers to deploy applications.

Those clients who engage with Kubernetes now, see challenges, for example, that there is a multitude of Kubernetes clusters in large organizations; they could even come from various different sources. There’s not very much to bring those Kubernetes clusters together so that there’s a lot more operational overhead.

“When we bring Cloud Foundry clients into the Kubernetes era, we help them providing the right toolset so that they can keep on creating Kubernetes clusters, and give them the tooling so that the life cycle management of workloads – both Cloud Foundry on Kubernetes, Cloud Foundry on BOSH, Kubernetes on BOSH and upcoming Kubernetes on Cluster API – will behave from the operator’s perspective as well as from the application developer’s perspective, if not identical then at least close to identical fashion, ” he said. “So life cycle management needs to be automated, and that’s a strong focus and a challenge that needs to be solved.”