- It will provide full application lifecycle automation and enable enterprises to shrink release cycles from months to minutes as per SUSE
- The enhancements to the platform’s web-based management console will help administrators manage applications more easily and securely
SUSE has announced the availability of SUSE Cloud Application Platform 2.0. It said that this will allow enterprises to transition existing Cloud Foundry implementations rapidly and pragmatically to modern, Kubernetes-based architecture. It will provide full application lifecycle automation and enable enterprises to shrink release cycles from months to minutes claimed the company.
The company said, “A new Kubernetes Operator in this release enables easier deployment and management of the Cloud Foundry-based platform on Kubernetes infrastructure. This 2.0 release is also simpler to install, operate, and maintain on Kubernetes platforms anywhere – on-premises and in public clouds. It also opens an accelerated and pragmatic path for existing Cloud Foundry users to transition to modern, Kubernetes-based architecture.”
Improved security with Helm 3
SUSE also said that enhancements to the platform’s web-based management console will help administrators manage applications more easily and securely. A new workload view will provide deeper insight into applications and their deployment settings. It also comes with improved security with Helm 3. It reduces threat surface by eliminating Tiller, the server-side component used in Helm 2, and defers access control directly to Kubernetes.
SUSE further said, “SUSE Cloud Application Platform 2.0 builds on and advances those efforts, incorporating several upstream technologies recently contributed by SUSE to the Cloud Foundry Community. These include KubeCF, a containerized version of the Cloud Foundry Application Runtime designed to run on Kubernetes, and project Quarks, a Kubernetes operator for automating deployment and management of Cloud Foundry on Kubernetes.”
SUSE helps current Cloud Foundry users to take advantage of new Kubernetes capabilities and speed their transition to a Kubernetes architecture. it does so by building from the upstream KubeCF project and incorporating new Kubernetes features regularly and incrementally.