Revise intro doc in zh (#318)
This commit is contained in:
Lei Zhang (Harry)
GitHub
parent
f4920b882f
commit
db8b163fed
|
|
@ -31,13 +31,23 @@ KubeVela is a modern application platform that makes it easier and faster to del
|
|||
|
||||
## Comparisons
|
||||
|
||||
### KubeVela vs. CI/CD systems
|
||||
|
||||
KubeVela is a CD (Continuous Delivery) control plane that works at downstream of your CI process. So you will reuse the CI process you already adopted and KubeVela will take over CD process by empowering it with modern application delivery best practices such as declarative CD workflow, programmable workflow steps, pull model, multi-cloud/cluster delivery, unified cloud resource provision/binding, and much more.
|
||||
|
||||
If you already adopted GitOps practice in CD section, KubeVela is even easier to fit in as it's fully declarative by design. All KubeVela features including CD workflow and multi-cloud/cluster delivery will be immediately available in your GitOps process by simply putting a KubeVela application YAML inside your configuration repository.
|
||||
|
||||
> Feel free to check the [Best Practices](https://kubevela.io/docs/case-studies/jenkins-cicd) documentation for more details.
|
||||
|
||||
### KubeVela vs. Platform-as-a-Service (PaaS)
|
||||
|
||||
The typical examples are Heroku and Cloud Foundry. They provide full application deployment and management capabilities and aim to improve developer experience and efficiency. In this context, KubeVela shares the same goal.
|
||||
|
||||
Though the biggest difference lies in **flexibility**.
|
||||
|
||||
KubeVela is fully programmable. All of its deployment workflow and component feature set are LEGO-style CUE modules and can be extended or removed in-place when your needs change. Comparatively, traditional PaaS systems are highly restricted, i.e. they have to enforce constraints in the supported types of applications and capabilities -- That means as the platform grows, you always outgrow the capabilities of the PaaS system. Growing and extending is so much easier to do in the KubeVela platform.
|
||||
KubeVela is fully programmable. All of its deployment workflow and component feature set are LEGO-style CUE modules and can be extended or removed in-place when your needs change. Comparatively, traditional PaaS systems are highly restricted, i.e. they have to enforce constraints in the supported types of applications and capabilities. When your needs expand, you always outgrow the capabilities of the PaaS system - this will never happen in KubeVela platform.
|
||||
|
||||
Also, as a CD control plane, KubeVela is working on top of runtime infrastructures (and we believe this is the right form for next-gen PaaS), while most existing PaaS systems tend to be installed as a plugin inside runtime cluster.
|
||||
|
||||
### KubeVela vs. Serverless
|
||||
|
||||
|
|
|
|||
|
|
@ -197,71 +197,41 @@
|
|||
"What is KubeVela?": {
|
||||
"message": "KubeVela 是什么？"
|
||||
},
|
||||
"KubeVela introduces the": {
|
||||
"message": "KubeVela 引入了"
|
||||
},
|
||||
"as the main API to capture a full deployment of microservices, and builds features around the application needs only. Progressive rollout and multi-cluster deployment are provided out-of-box. No infrastructure level concerns, simply deploy.": {
|
||||
"message": "作为主要的 API，以声明全部的微服务，并只围绕应用程序的需求建立功能。开箱即用的灰度发布和多集群部署功能。无需关心基础设施层面的问题，只要部署即可。"
|
||||
},
|
||||
"and/or": {
|
||||
"message": "和/或"
|
||||
},
|
||||
"Application Centric": {
|
||||
"message": "完全以应用为中心"
|
||||
},
|
||||
"Leveraging Open Application Model (OAM), KubeVela introduces consistent yet higher level API to capture a full deployment of microservices on top of hybrid environments. Placement strategy, traffic shifting and rolling update are declared at application level. No infrastructure level concern, simply deploy.": {
|
||||
"message": "Leveraging Open Application Model (OAM), KubeVela introduces consistent yet higher level API to capture a full deployment of microservices on top of hybrid environments. Placement strategy, traffic shifting and rolling update are declared at application level. No infrastructure level concern, simply deploy."
|
||||
},
|
||||
"KubeVela introduces Open Application Model (OAM) as the consistent yet higher level API to capture a full deployment of microservices on top of hybrid environments. Placement strategy, traffic shifting and rolling update are declared at application level. No infrastructure level concern, simply deploy.": {
|
||||
"message": "KubeVela 基于开放应用模型 (OAM) 提供了抽象且对于不同基础设施一致的 API，从而使得微服务模式下的异构组件可以在混合环境中部署和编排。分发策略、流量控制和滚动更新均可以在应用程序中声明式的描述。无需担心基础架构细节，只需部署即可。"
|
||||
},
|
||||
"Natively Extensible": {
|
||||
"message": "Natively Extensible"
|
||||
},
|
||||
"KubeVela uses": {
|
||||
"message": "KubeVela uses"
|
||||
},
|
||||
"to glue capabilities (e.g. workload types, operational behaviors, and cloud services) provided by runtime infrastructure and expose them to users via self-service API. When users' needs grow, these API can naturally expand in programmable approach. No restriction, fully flexible.": {
|
||||
"message": "to glue capabilities (e.g. workload types, operational behaviors, and cloud services) provided by runtime infrastructure and expose them to users via self-service API. When users' needs grow, these API can naturally expand in programmable approach. No restriction, fully flexible."
|
||||
},
|
||||
"Runtime Agnostic": {
|
||||
"message": "基础设施无关"
|
||||
"KubeVela introduces Open Application Model (OAM) as the consistent yet higher level API to capture and render a full deployment of microservices on top of hybrid environments. Placement strategy, traffic shifting and rolling update are declared at application level. No infrastructure level concern, simply deploy.": {
|
||||
"message": "KubeVela 以开放应用模型（OAM）作为应用交付的顶层抽象，并通过声明式的交付工作流来捕获面向混合环境的微服务应用交付的整个过程，甚至连多集群分发策略、流量调配和滚动更新等运维特征，也都声明在应用级别。用户无需关心任何基础设施细节，只需要专注于定义和部署应用即可。"
|
||||
},
|
||||
"Programmable Workflow": {
|
||||
"message": "可编程式交付工作流"
|
||||
},
|
||||
"KubeVela leverages ": {
|
||||
"message": "KubeVela 利用"
|
||||
"KubeVela models application delivery as DAG (Directed Acyclic Graph) and expresses it with CUE - a modern data configuration language. This allows you to design application deployment steps per needs and orchestrate them in programmable approach. No restrictions, natively extensible.": {
|
||||
"message": "KubeVela 会将应用交付流程建模为有向无环图（DAG），并将它通过 CUE（一种源自 Google Borg 系统的数据配置语言）来进行表达和实现。这使得你可以自由的根据自己的需求来设计交付工作流中的每一个步骤，并通过可编程的方式将它们编排起来。没有任何限制，原生高可扩展"
|
||||
},
|
||||
" CUE": {
|
||||
"message": "CUE"
|
||||
"Infrastructure Agnostic": {
|
||||
"message": "基础设施无关"
|
||||
},
|
||||
"to implement its model layer. This allows you to define an application deployment workflow as DAG, with all steps and application's needs glued together in programmable approach. No restrictions, natively extensible.": {
|
||||
"message": "来实现其模型层。这允许您将应用程序部署工作流定义为 DAG，将所有步骤和应用程序需求以可编程方式粘合在一起。没有限制，原生可扩展。"
|
||||
},
|
||||
"KubeVela is built with Kubernetes as control plane but adaptable to any runtime as data-plane. It can deploy (and manage) diverse workload types such as container, cloud functions, databases, or even EC2 instances across hybrid environments. Also, this means KubeVela seamlessly works with any Kubernetes compatible CI/CD or GitOps tools via declarative API.": {
|
||||
"message": "KubeVela 作为控制平面可以适应任何运行时。它可以跨混合环境部署和管理不同的工作负载类型，例如容器、云资源、数据库，甚至 EC2 实例。KubeVela 通过声明式 API 同任何与 Kubernetes 兼容的 CI/CD 或 GitOps 工具无缝协作。"
|
||||
},
|
||||
"KubeVela works as an application delivery control plane that is fully runtime agnostic. It can deploy and operate any application components including containers, cloud functions, databases, or even EC2 instances across hybrid environments, following the workflow you defined.": {
|
||||
"message": "KubeVela 作为一个控制平面，在应用程序交付过程中完全与运行时无关。它可以按照您定义的工作流，在混合环境中部署和操作任何应用程序组件，包括容器、云功能、数据库甚至 EC2 实例。"
|
||||
"KubeVela works as an application delivery control plane that is fully decoupled from runtime infrastructure. It can deploy any workload types including containers, cloud services, databases, or even VM instances to any cloud or Kubernetes cluster, following the workflow designed by you.": {
|
||||
"message": "KubeVela 本质上是一个与运行时基础设施无关的应用交付与管理控制平面。所以它可以按照你定义的工作流与策略，面向任何环境交付和管理任何应用组件，比如：容器、云函数、数据库，甚至网络和虚拟机实例等等。"
|
||||
},
|
||||
"KubeVela is a": {
|
||||
"message": "KubeVela 是"
|
||||
"message": "KubeVela 是一个"
|
||||
},
|
||||
"sandbox project": {
|
||||
"message": "sandbox 项目"
|
||||
"message": "沙箱级项目"
|
||||
},
|
||||
"KubeVela is a modern application platform that makes deploying and managing applications across today's hybrid, multi-cloud environments": {
|
||||
"message": "KubeVela 是一个现代应用程序平台，适用于在当今的混合多云环境中部署和管理应用程序。"
|
||||
"KubeVela is a modern application delivery platform that makes deploying and operating applications across today's hybrid, multi-cloud environments": {
|
||||
"message": "KubeVela 是一个现代化的应用交付平台，它可以让你的应用交付与管理在当今流行的混合、多云环境中变得更加"
|
||||
},
|
||||
"easier and faster.": {
|
||||
"message": "更简单且轻松。"
|
||||
" easier, faster and more reliable.": {
|
||||
"message": "简单、轻松、可靠。"
|
||||
},
|
||||
"KubeVela is runtime agnostic, natively extensible, yet most importantly,": {
|
||||
"message": "KubeVela 不锁定运行时，原生可扩展。最重要的是，"
|
||||
"KubeVela is infrastructure agnostic, programmable, yet most importantly,": {
|
||||
"message": "KubeVela 是基础设施无关的、可编程的，但最重要的是："
|
||||
},
|
||||
"application-centric.": {
|
||||
"message": "以应用为中心。"
|
||||
"message": "它是完全以应用为中心的。"
|
||||
},
|
||||
".": {
|
||||
"message": "."
|
||||
|
|
|
|||
|
|
@ -23,7 +23,7 @@ KubeVela 通过以下设计，使得面向混合/多云环境的应用交付变
|
|||
|
||||
- **完全以应用为中心** - KubeVela 创新性的提出了[开放应用模型（OAM）](https://oam.dev/)来作为应用交付的顶层抽象，并通过声明式的交付工作流来捕获面向混合环境的微服务应用交付的整个过程，甚至连多集群分发策略、流量调配和滚动更新等运维特征，也都声明在应用级别。用户无需关心任何基础设施细节，只需要专注于定义和部署应用即可。
|
||||
- **可编程式交付工作流** - KubeVela 的交付模型是利用 [CUE](https://cuelang.org/) 来实现的。CUE 是一种诞生自 Google Borg 系统的数据配置语言，它可以将应用交付的所有步骤、所需资源、关联的运维动作以可编程的方式粘合成一个 DAG（有向无环图）来作为最终的声明式交付计划。相比于其他系统的复杂性和不可扩展性，KubeVela 基于 CUE 的实现不仅使用简单、扩展性极强，也更符合现代 GitOps 应用交付的趋势与要求。
|
||||
- **运行时无关** - KubeVela 是一个完全与运行时基础设施无关的应用交付与管理控制平面。所以它可以按照你定义的工作流与策略，面向任何环境交付和管理任何应用组件，比如：容器、云函数、数据库，甚至 AWS EC2 实例等等。
|
||||
- **基础设施无关** - KubeVela 是一个完全与运行时基础设施无关的应用交付与管理控制平面。所以它可以按照你定义的工作流与策略，面向任何环境交付和管理任何应用组件，比如：容器、云函数、数据库，甚至 网络和虚拟机实例等等。
|
||||
|
||||
## 谁应该使用 KubeVela？
|
||||
|
||||
|
|
@ -37,13 +37,24 @@ KubeVela 通过以下设计，使得面向混合/多云环境的应用交付变
|
|||
|
||||
## 产品形态对比
|
||||
|
||||
### KubeVela vs. CI/CD 系统
|
||||
|
||||
KubeVela 是一个工作在 CI 流程下游的 CD 控制平面（Continuous Delivery Control Plane）。所以 KubeVela 希望你保持现有的 CI 流程，而在需要开始制品部署时让 KubeVela 接管 CD 流程。KubeVela 会给你的 CD 流程带来大量的现代化应用交付最佳实践，比如：声明式交付工作流、可编程的工作流步骤、Pull 模型、多云/多集群交付流程、统一的云服务部署和绑定等等。
|
||||
|
||||
如果你已经在 CD 环节中采纳了 GitOps 实践，KubeVela 会更容易跟你的 CI/CD 系统集成，因为 KubeVela 是完全声明式的。只需要把 KubeVela 的应用部署描述文件放置在你的配置仓库当中，所有的 KubeVela 特性（包括声明式交付工作流、多云/多集群交付流程等）就会立刻在你 的 GitOps 流程中出现。
|
||||
|
||||
> 欢迎查阅 [《最佳实践》](case-studies/jenkins-cicd) 文档来了解更多关于 KubeVela 与各类 CI/CD 系统协作的实践.
|
||||
|
||||
|
||||
### KubeVela vs. 平台即服务 (PaaS)
|
||||
|
||||
典型的例子是 Heroku 和 Cloud Foundry。 它们提供完整的应用程序部署和管理功能，旨在提高开发人员的体验和效率。在这个情况下，KubeVela 也有着相同的目标。
|
||||
典型的例子是 Heroku 和 Cloud Foundry。 它们提供完整的应用程序部署和管理功能，旨在提高开发人员的体验和效率。在这个场景下，KubeVela 也有着相同的目标。
|
||||
|
||||
不过，KubeVela 和它们最大的区别在于其**可扩展性**。
|
||||
|
||||
KubeVela 对待交付应用没有任何限制，它的整个应用交付与管理能力集也是由独立的可插拔模块（CUE 模块）构成的，这些模块可以随时通过编写 CUE 模板的方式进行增加或者定制。与这种机制相比，传统的 PaaS 系统的限制非常多：它们需要对应用类型和提供的能力进行各种约束来实现更好的用户体验，但随着应用交付需求的增长，用户的诉求就一定会超出 PaaS 系统的能力边界。这种情况在 KubeVela 平台中则永远不会发生。
|
||||
KubeVela 是可编程的。它的交付工作流乃至整个应用交付与管理能力集都是由独立的可插拔模块构成的，这些模块可以随时通过编写 CUE 模板的方式进行增/删/重定义且变更会即时生效。与这种机制相比，传统的 PaaS 系统的限制非常多：它们需要对应用类型和提供的能力进行各种约束来实现更好的用户体验，但随着应用交付需求的增长，用户的诉求就一定会超出 PaaS 系统的能力边界。这种情况在 KubeVela 平台中则永远不会发生。
|
||||
|
||||
此外，KubeVela 是一个独立于运行时集群的应用交付控制平面（这是我们认为的下一代 PaaS 系统的合理形态），而现有的 PaaS 则往往选择以插件形式部署在运行时集群当中。
|
||||
|
||||
### KubeVela vs. Serverless
|
||||
|
||||
|
|
@ -67,7 +78,7 @@ KubeVela 作为一个应用交付系统天然可以部署各种制品类型，
|
|||
|
||||
### KubeVela vs. Kubernetes
|
||||
|
||||
KubeVela 是一个基于云原生技术栈构建的现代应用交付系统。它利用了开放应用程序模型（Open Application Model）和 Kubernetes 来解决一个旷日已久的难题——如何让应用交付变得更加轻松愉快。
|
||||
KubeVela 是一个基于云原生技术栈构建的现代应用交付系统。它利用了开放应用程序模型（Open Application Model）和 Kubernetes 作为控制平面来解决一个旷日已久的难题——如何让应用交付变得更加轻松愉快。
|
||||
|
||||
## 下一步
|
||||
|
||||
|
|
|
|||
Binary file not shown.
|
Before Width: | Height: | Size: 198 KiB After Width: | Height: | Size: 272 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 506 KiB After Width: | Height: | Size: 149 KiB |
|
|
@ -17,13 +17,13 @@ slug: /
|
|||
|
||||
KubeVela 是一个开箱即用的、现代化的应用交付与管理平台。
|
||||
|
||||
|
||||
|
||||
|
||||
KubeVela 通过以下设计，使得面向混合/多云环境的应用交付变得非常简单高效：
|
||||
|
||||
- **完全以应用为中心** - KubeVela 提出了[开放应用模型（OAM）](https://oam.dev/)来作为应用交付的顶层抽象，并通过声明式的交付工作流来捕获和渲染面向混合环境的微服务应用交付的整个过程，甚至连多集群分发策略、流量调配和滚动更新等运维特征，也都声明在应用级别。用户无需关心任何基础设施细节，只需要专注于定义和部署应用即可。
|
||||
- **可编程式交付工作流** - KubeVela 的交付模型是利用 [CUE](https://cuelang.org/) 来实现的。CUE 是一种诞生自 Google Borg 系统的数据配置语言，它可以将应用交付的所有步骤、所需资源、关联的运维动作以可编程的方式编排成一个 DAG（有向无环图）来作为最终的声明式交付计划。相比于其他系统的复杂性和不可扩展性，KubeVela 基于 CUE 的实现不仅使用简单、扩展性极强，也更符合现代 GitOps 应用交付的趋势与要求。
|
||||
- **基础设施无关** - KubeVela 是一个完全与运行时基础设施无关的应用交付与管理控制平面。所以它可以按照你定义的工作流与策略交付任何工作负载，比如：容器、云函数、数据库、甚至虚拟机实例到任何云或者 Kubernetes 集群当中。
|
||||
- **完全以应用为中心** - KubeVela 创新性的提出了[开放应用模型（OAM）](https://oam.dev/)来作为应用交付的顶层抽象，并通过声明式的交付工作流来捕获面向混合环境的微服务应用交付的整个过程，甚至连多集群分发策略、流量调配和滚动更新等运维特征，也都声明在应用级别。用户无需关心任何基础设施细节，只需要专注于定义和部署应用即可。
|
||||
- **可编程式交付工作流** - KubeVela 的交付模型是利用 [CUE](https://cuelang.org/) 来实现的。CUE 是一种诞生自 Google Borg 系统的数据配置语言，它可以将应用交付的所有步骤、所需资源、关联的运维动作以可编程的方式粘合成一个 DAG（有向无环图）来作为最终的声明式交付计划。相比于其他系统的复杂性和不可扩展性，KubeVela 基于 CUE 的实现不仅使用简单、扩展性极强，也更符合现代 GitOps 应用交付的趋势与要求。
|
||||
- **基础设施无关** - KubeVela 是一个完全与运行时基础设施无关的应用交付与管理控制平面。所以它可以按照你定义的工作流与策略，面向任何环境交付和管理任何应用组件，比如：容器、云函数、数据库，甚至 网络和虚拟机实例等等。
|
||||
|
||||
## 谁应该使用 KubeVela？
|
||||
|
||||
|
|
@ -37,13 +37,24 @@ KubeVela 通过以下设计，使得面向混合/多云环境的应用交付变
|
|||
|
||||
## 产品形态对比
|
||||
|
||||
### KubeVela vs. CI/CD 系统
|
||||
|
||||
KubeVela 是一个工作在 CI 流程下游的 CD 控制平面（Continuous Delivery Control Plane）。所以 KubeVela 希望你保持现有的 CI 流程，而在需要开始制品部署时让 KubeVela 接管 CD 流程。KubeVela 会给你的 CD 流程带来大量的现代化应用交付最佳实践，比如：声明式交付工作流、可编程的工作流步骤、Pull 模型、多云/多集群交付流程、统一的云服务部署和绑定等等。
|
||||
|
||||
如果你已经在 CD 环节中采纳了 GitOps 实践，KubeVela 会更容易跟你的 CI/CD 系统集成，因为 KubeVela 是完全声明式的。只需要把 KubeVela 的应用部署描述文件放置在你的配置仓库当中，所有的 KubeVela 特性（包括声明式交付工作流、多云/多集群交付流程等）就会立刻在你 的 GitOps 流程中出现。
|
||||
|
||||
> 欢迎查阅 [《最佳实践》](case-studies/jenkins-cicd) 文档来了解更多关于 KubeVela 与各类 CI/CD 系统协作的实践.
|
||||
|
||||
|
||||
### KubeVela vs. 平台即服务 (PaaS)
|
||||
|
||||
典型的例子是 Heroku 和 Cloud Foundry。 它们提供完整的应用程序部署和管理功能，旨在提高开发人员的体验和效率。在这个情况下，KubeVela 也有着相同的目标。
|
||||
典型的例子是 Heroku 和 Cloud Foundry。 它们提供完整的应用程序部署和管理功能，旨在提高开发人员的体验和效率。在这个场景下，KubeVela 也有着相同的目标。
|
||||
|
||||
不过，KubeVela 和它们最大的区别在于其**可扩展性**。
|
||||
|
||||
KubeVela 是可编程的。它的交付工作流乃至整个应用交付与管理能力集都是完全由独立的可插拔模块构成的，这些模块可以随时通过编写 CUE 模板的方式进行增/删/重定义且变更会即时生效。与这种机制相比，传统的 PaaS 系统的限制非常多：它们需要对应用类型和提供的能力进行各种约束来实现更好的用户体验，但随着应用交付需求的增长，用户的诉求就一定会超出 PaaS 系统的能力边界。这种情况在 KubeVela 平台中则永远不会发生。
|
||||
KubeVela 是可编程的。它的交付工作流乃至整个应用交付与管理能力集都是由独立的可插拔模块构成的，这些模块可以随时通过编写 CUE 模板的方式进行增/删/重定义且变更会即时生效。与这种机制相比，传统的 PaaS 系统的限制非常多：它们需要对应用类型和提供的能力进行各种约束来实现更好的用户体验，但随着应用交付需求的增长，用户的诉求就一定会超出 PaaS 系统的能力边界。这种情况在 KubeVela 平台中则永远不会发生。
|
||||
|
||||
此外，KubeVela 是一个独立于运行时集群的应用交付控制平面（这是我们认为的下一代 PaaS 系统的合理形态），而现有的 PaaS 则往往选择以插件形式部署在运行时集群当中。
|
||||
|
||||
### KubeVela vs. Serverless
|
||||
|
||||
|
|
@ -67,7 +78,7 @@ KubeVela 作为一个应用交付系统天然可以部署各种制品类型，
|
|||
|
||||
### KubeVela vs. Kubernetes
|
||||
|
||||
KubeVela 是一个基于云原生技术栈构建的现代应用交付系统。它利用了开放应用程序模型（Open Application Model）和 Kubernetes 来解决一个旷日已久的难题——如何让应用交付变得更加轻松愉快。
|
||||
KubeVela 是一个基于云原生技术栈构建的现代应用交付系统。它利用了开放应用程序模型（Open Application Model）和 Kubernetes 作为控制平面来解决一个旷日已久的难题——如何让应用交付变得更加轻松愉快。
|
||||
|
||||
## 下一步
|
||||
|
||||
|
|
|
|||
Binary file not shown.
|
Before Width: | Height: | Size: 198 KiB After Width: | Height: | Size: 272 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 506 KiB After Width: | Height: | Size: 149 KiB |
|
|
@ -9,11 +9,7 @@ const features = [
|
|||
<>
|
||||
<p>
|
||||
<Translate>
|
||||
KubeVela introduces Open Application Model (OAM) as the consistent
|
||||
yet higher level API to capture and render a full deployment of microservices
|
||||
on top of hybrid environments. Placement strategy, traffic shifting
|
||||
and rolling update are declared at application level.
|
||||
No infrastructure level concern, simply deploy.
|
||||
KubeVela introduces Open Application Model (OAM) as the consistent yet higher level API to capture and render a full deployment of microservices on top of hybrid environments. Placement strategy, traffic shifting and rolling update are declared at application level. No infrastructure level concern, simply deploy.
|
||||
</Translate>
|
||||
</p>
|
||||
</>
|
||||
|
|
@ -26,13 +22,7 @@ const features = [
|
|||
<>
|
||||
<p>
|
||||
<Translate>
|
||||
KubeVela models application delivery as DAG (Directed Acyclic Graph)
|
||||
and expresses it with</Translate>
|
||||
<a href="https://github.com/cuelang/cue"> CUE</a>, <Translate>
|
||||
a modern data configuration language. This allows you to design
|
||||
application deployment steps per needs and
|
||||
orchestrate them in programmable approach. No restrictions,
|
||||
natively extensible.</Translate>
|
||||
KubeVela models application delivery as DAG (Directed Acyclic Graph) and expresses it with CUE - a modern data configuration language. This allows you to design application deployment steps per needs and orchestrate them in programmable approach. No restrictions, natively extensible.</Translate>
|
||||
</p>
|
||||
</>
|
||||
),
|
||||
|
|
|
|||
|
|
@ -84,7 +84,7 @@ export default function Home() {
|
|||
<div className={clsx('hero', styles.hero)}>
|
||||
<div className="container text--center">
|
||||
<h3 className="hero__subtitle">
|
||||
<Translate>KubeVela is a</Translate> <a href="https://cncf.io/">Cloud Native Computing Foundation</a> <Translate>sandbox project</Translate>
|
||||
<Translate>KubeVela is a</Translate> <a href="https://cncf.io/">CNCF (Cloud Native Computing Foundation)</a> <Translate>sandbox project</Translate>
|
||||
</h3>
|
||||
<div className={clsx('cncf-logo', styles.cncfLogo)} />
|
||||
</div>
|
||||
|
|
@ -102,9 +102,8 @@ const WhatIs = () => (
|
|||
<p className="hero__subtitle">
|
||||
<small>
|
||||
<Translate>
|
||||
KubeVela is a modern application platform that makes deploying and managing applications
|
||||
across today's hybrid, multi-cloud environments
|
||||
</Translate> <i> <Translate>easier and faster.</Translate> </i>
|
||||
KubeVela is a modern application delivery platform that makes deploying and operating applications across today's hybrid, multi-cloud environments
|
||||
</Translate><i><Translate> easier, faster and more reliable.</Translate></i>
|
||||
<br />
|
||||
<br />
|
||||
<Translate>
|
||||
|
|
|
|||
|
|
@ -19,6 +19,7 @@ KubeVela is a modern application platform that makes it easier and faster to del
|
|||
|
||||
|
||||
|
||||
|
||||
## Who should use KubeVela?
|
||||
|
||||
- Application developers, operators, DevOps engineers
|
||||
|
|
@ -30,13 +31,23 @@ KubeVela is a modern application platform that makes it easier and faster to del
|
|||
|
||||
## Comparisons
|
||||
|
||||
### KubeVela vs. CI/CD systems
|
||||
|
||||
KubeVela is a CD (Continuous Delivery) control plane that works at downstream of your CI process. So you will reuse the CI process you already adopted and KubeVela will take over CD process by empowering it with modern application delivery best practices such as declarative CD workflow, programmable workflow steps, pull model, multi-cloud/cluster delivery, unified cloud resource provision/binding, and much more.
|
||||
|
||||
If you already adopted GitOps practice in CD section, KubeVela is even easier to fit in as it's fully declarative by design. All KubeVela features including CD workflow and multi-cloud/cluster delivery will be immediately available in your GitOps process by simply putting a KubeVela application YAML inside your configuration repository.
|
||||
|
||||
> Feel free to check the [Best Practices](https://kubevela.io/docs/case-studies/jenkins-cicd) documentation for more details.
|
||||
|
||||
### KubeVela vs. Platform-as-a-Service (PaaS)
|
||||
|
||||
The typical examples are Heroku and Cloud Foundry. They provide full application deployment and management capabilities and aim to improve developer experience and efficiency. In this context, KubeVela shares the same goal.
|
||||
|
||||
Though the biggest difference lies in **flexibility**.
|
||||
|
||||
KubeVela is fully programmable. All of its deployment workflow and component feature set are LEGO-style CUE modules and can be extended or removed in-place when your needs change. Comparatively, traditional PaaS systems are highly restricted, i.e. they have to enforce constraints in the supported types of applications and capabilities -- That means as the platform grows, you always outgrow the capabilities of the PaaS system. Growing and extending is so much easier to do in the KubeVela platform.
|
||||
KubeVela is fully programmable. All of its deployment workflow and component feature set are LEGO-style CUE modules and can be extended or removed in-place when your needs change. Comparatively, traditional PaaS systems are highly restricted, i.e. they have to enforce constraints in the supported types of applications and capabilities. When your needs expand, you always outgrow the capabilities of the PaaS system - this will never happen in KubeVela platform.
|
||||
|
||||
Also, as a CD control plane, KubeVela is working on top of runtime infrastructures (and we believe this is the right form for next-gen PaaS), while most existing PaaS systems tend to be installed as a plugin inside runtime cluster.
|
||||
|
||||
### KubeVela vs. Serverless
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue