截至本文发稿(2019-2-10, 农历大年初六)时为止,访问SAP云平台的官方网站:https://cloudplatform.sap.com...

能看到下面的网页:SAP云平台上的Kubernetes环境,Coming Soon(即将推出)

Build powerful container-native applications and deploy them on a cloud or infrastructure of your choice without worrying about the creation and management of the underlying container clusters.

我来翻译一下:SAP云平台的Kubernetes编程环境能让编程人员开发功能强大的容器原生应用并顺利部署在云上,而不用担心底层容器集群的创建和管理。

为什么SAP云平台要选择支持Kubernetes?

Containers are rapidly becoming a popular development paradigm for cloud-native applications in the industry – with Kubernetes as the dominant container orchestrations technology. The SAP Cloud Platform Kubernetes environment reduces pain points associated with the creation and management of Kubernetes clusters by offering an easy to use, secure and open standards-based Cluster-as-a-Service running on top of a variety of underlying infrastructure choices, deployment options of cloud vs. on-premise, etc. SAP is making this innovation accessible to the entire developer community via an open-source project called Gardener.

SAP给出的答案是:基于Kubernetes的容器编排技术近年来已经成为行业里最流行的云原生应用开发范式之一。SAP云平台的Kubernetes编程环境提供了一种简易,安全,基于业界标准的方式提供了对Kubernetes集群的创建和管理,这种方式基于Cluster-as-a-Service(集群即服务)的方式运作,能运行在多种底层云技术设施上,解决了开发人员需要花大量时间学习Kubernetes底层细节的痛点。

这种Cluster-as-a-Service的服务,SAP通过开源项目Gardener提供访问:
https://gardener.cloud/

更多Gardener的使用方式和截图,请参考我的文章:
站在巨人肩膀上的牛顿:Kubernetes和SAP Kyma
https://www.jianshu.com/p/c85...

使用SAP云平台的Kubernetes编程环境能享受哪些收益

  1. Customers can rely upon the SAP Cloud Platform to create, manage, secure and maintain the container clusters for them.

客户可以直接使用SAP云平台创建和管理容器集群

  1. Leverage the Gardener open-source project to easily access a variety of community innovations.

借助Gardener这个开源项目享受到开源社区的种种创新

  1. Use container-native development to build and operate complex, stateful cloud applications that require greater freedom over underlying infrastructure.

通常情况下开发复杂的云原生应用和有状态的云应用,需要对底层云的基础设施具有很高的自由度。而SAP云平台通过Gardener提供的Cluster-as-a-Service, 给使用者提供了这种自由度。

要获取更多Jerry的原创文章,请关注公众号"汪子熙":


注销
1k 声望1.6k 粉丝

invalid