Chore: refine readme (#647)
Signed-off-by: Jianbo Sun <jianbo.sjb@alibaba-inc.com>
This commit is contained in:
Jianbo Sun
GitHub
parent
408554ce3b
commit
2a90ec5e0b
|
|
@ -7,24 +7,24 @@ slug: /
|
|||
|
||||
KubeVela is a modern software delivery platform that makes it easier and faster to deliver and manage applications across hybrid, multi-cloud environments.
|
||||
|
||||
Using KubeVela, software teams can build cloud native applications per needs as they grow, then run them anywhere.
|
||||
Using KubeVela, software teams can build cloud native applications per needs as they grow, then deliver them anywhere.
|
||||
|
||||
|
||||
|
||||
|
||||
## Key Features
|
||||
|
||||
* **Unified Application Delivery Model**
|
||||
* **Unified Application Delivery Experience**
|
||||
|
||||
KubeVela introduces a [unified and cross-platform delivery model(OAM)](https://oam.dev/) that allows you to deploy any workload type, including containers, databases, or even VM instances to any cloud or Kubernetes clusters. It helps you to just write application once, and deliver it the same everywhere, no more re-writing everything from scratch for any new delivery target.
|
||||
|
||||
* **Intention-driven Delivery Workflow**
|
||||
* **Automated Deployment across Clusters**
|
||||
|
||||
The whole delivery model was fully intention-driven, having both user experience and robustness. The implementation is driven by CUE - a powerful configuration language developed at Google, and runs on Kubernetes with reconciliation loops. This allows you to design application deployment steps per needs, satisfy the fast growth of businesses requirements, while also keep your production safe with continuous enforcement.
|
||||
KubeVela natively supports rich continuous delivery strategies in various multi-cluster/hybrid-cloud scenarios or mixed environments. These strategies provides efficiency and safety to the distributed delivery process. The centralized management reduces the burden of looking over each clusters and gives unified experience across platforms. With KubeVela, you don't need to have any Ph.D. degree in Kubernetes to run automatic deployments.
|
||||
|
||||
* **Declarative and Highly Extensible Workflow**
|
||||
|
||||
* **Multi-cluster/Hybrid-cloud Continuous Delivery Control Plane**
|
||||
|
||||
KubeVela natively supports rich continuous delivery policies in various multi-cluster/hybrid-cloud scenarios or mixed environments, it supports cross-environment promotion as well. It can enhance the CI/CD pipeline by serving as unified control plane, while it is also capable of leveraging GitOps to automate continuous delivery process in the style of IaC.
|
||||
The application delivery process is driven by declarative workflow. Executed by reconciliation loops with limited privileges, the workflow is both robust and secure enough to prevent any unexpected configuration drifts. Users can also make arbitrary reusable customizations to the workflow through writing CUE definitions. The extensibility will always satisfy your growing business demands while keeping your production safe with continuous enforcement at the same time.
|
||||
|
||||
|
||||
## KubeVela vs. Other Software
|
||||
|
|
@ -37,10 +37,10 @@ KubeVela is a continuous delivery platform that works at downstream of your CI p
|
|||
|
||||
### KubeVela vs. GitOps (ArgoCD, FluxCD, etc.)
|
||||
|
||||
KubeVela does not replace your GitOps process: it improves it by adding a unified control plane on top of it.
|
||||
KubeVela adopts your GitOps process and improves it by adding multi-cluster/hybrid-cloud capabilities:
|
||||
|
||||
* KubeVela can provide cross-environment promotion for your multi-cluster/hybrid-cloud applications, it adopts major of your existing tools for the underlying GitOps driver.
|
||||
* KubeVela has a user-friendly delivery model that _reduces any lock-in_, you can change any underlying tools without rewriting all your application.
|
||||
* KubeVela has a user-friendly and programable workflow that allows you to integrate any of your delivery steps, including approval and notification flows.
|
||||
* With the help of the workflow, KubeVela can provide cross-environment promotion for your multi-cluster/hybrid-cloud applications.
|
||||
|
||||
|
||||
### KubeVela vs. PaaS (Heroku, Cloud Foundry, etc.)
|
||||
|
|
|
|||
|
|
@ -325,7 +325,7 @@ z ?:float
|
|||
```
|
||||
|
||||
Optional variables can be skipped, that usually works together with conditional logic.
|
||||
Specifically, if some field does not exit, the CUE grammar is `if _variable_ != _|_`, the example is like below:
|
||||
Specifically, if some field does not exist, the CUE grammar is `if _variable_ != _|_`, the example is like below:
|
||||
|
||||
```
|
||||
parameter: {
|
||||
|
|
|
|||
|
|
@ -197,23 +197,23 @@
|
|||
"What is KubeVela?": {
|
||||
"message": "KubeVela 是什么？"
|
||||
},
|
||||
"Unified Application Delivery Model": {
|
||||
"Unified Application Delivery Experience": {
|
||||
"message": "统一的应用交付模型"
|
||||
},
|
||||
"KubeVela introduces a unified and cross-platform delivery model(OAM) that allows you to deploy any workload type, including containers, databases, or even VM instances to any cloud or Kubernetes clusters. It helps you to just write application once, and deliver it the same everywhere, no more re-writing everything from scratch for any new delivery target.": {
|
||||
"message": "KubeVela 创新性的提出了开放应用模型（OAM）来作为应用交付的顶层抽象，该模型支持交付任意类型的工作负载包括容器、数据库甚至是虚拟机到不同的云和 Kubernetes 集群中。用户无需关心任何基础设施细节，只需要专注于定义和部署应用即可。应用只需要一次编排，就可以随处运行，免去了适配不同平台的痛苦。"
|
||||
},
|
||||
"Intention-driven Delivery Workflow": {
|
||||
"message": "声明式交付工作流"
|
||||
"Automated Deployment across Clusters": {
|
||||
"message": "自动化跨集群交付"
|
||||
},
|
||||
"The whole delivery model was fully intention-driven, having both user experience and robustness. The implementation is driven by CUE - a powerful configuration language developed at Google, and runs on Kubernetes with reconciliation loops. This allows you to design application deployment steps per needs, satisfy the fast growth of businesses requirements, while also keep your production safe with continuous enforcement.": {
|
||||
"message": "KubeVela 的整个交付模型完全是由用户声明式驱动的，兼顾用户体验和健壮性。实现层通过 CUE 语言（一种源自 Google Borg 系统的数据配置语言）保证可扩展性，运行在 Kubernetes 持续进行控制循环。这使得你可以自由的根据需求场景来设计和选用交付工作流中的每一个步骤，满足业务快速增长的需求，同时持续保证生产环境面向终态的稳定性。"
|
||||
"The application delivery process is driven by declarative workflow. Executed by reconciliation loops with limited privileges, the workflow is both robust and secure enough to prevent any unexpected configuration drifts. Users can also make arbitrary reusable customizations to the workflow through writing CUE definitions. The extensibility will always satisfy your growing business demands while keeping your production safe with continuous enforcement.": {
|
||||
"message": "KubeVela 的整个交付模型完全是由用户声明式驱动的，兼顾用户体验和健壮性，其控制循环能够有效避免配置漂移，且具备多租权限控制能力。用户可以通过 CUE 语言（一种源自 Google Borg 系统的数据配置语言）自由的根据需求场景来设计和选用交付工作流中的每一个步骤，满足业务快速增长的需求，同时持续保证生产环境面向终态的稳定性。"
|
||||
},
|
||||
"Multi-cluster/Hybrid-cloud Continuous Delivery Control Plane": {
|
||||
"message": "多集群/混合云应用交付控制平面"
|
||||
"Declarative and Highly Extensible Workflow": {
|
||||
"message": "声明式高可扩展工作流"
|
||||
},
|
||||
"KubeVela natively supports rich continuous delivery policies in various multi-cluster/hybrid-cloud scenarios or mixed environments, it supports cross-environment promotion as well. It can enhance the CI/CD pipeline by serving as unified control plane, while it is also capable of leveraging GitOps to automate continuous delivery process in the style of IaC.": {
|
||||
"message": "KubeVela 原生支持丰富的多集群/混合环境持续交付策略，也支持跨环境交付。它既可作为统一的持续交付控制平面增强现有 CI/CD 流水线，也可以满足现代 GitOps 应用交付的趋势与要求，以基础设施即代码（IaC）的方式来驱动持续交付过程。"
|
||||
"KubeVela natively supports rich continuous delivery strategies in various multi-cluster/hybrid-cloud scenarios or mixed environments. These strategies provides efficiency and safety to the distributed delivery process. The centralized management reduces the burden of looking over each clusters and gives unified experience across platforms. With KubeVela, you don't need to have any Ph.D. degree in Kubernetes to run automatic deployments.": {
|
||||
"message": "KubeVela 原生支持丰富的多集群/混合环境持续交付策略，也支持跨环境交付。这些交付策略为你的分布式交付流程提供了充足的效率和安全的保证。KubeVela 提供的中心化管控能力也减轻了到每一个集群去排查问题的负担，针对不同的平台提供统一的体验，为了享受自动化交付的便利，你再也不需要成为 Kubernetes 专家。"
|
||||
},
|
||||
"KubeVela is a": {
|
||||
"message": "KubeVela 是一个"
|
||||
|
|
|
|||
|
|
@ -27,11 +27,11 @@ KubeVela 是一个开箱即用的现代化应用交付与管理平台，它使
|
|||
|
||||
- **声明式交付工作流**
|
||||
|
||||
KubeVela 的整个交付模型完全是由用户声明式驱动的，兼顾用户体验和健壮性。实现层通过 [CUE 语言](https://cuelang.org/)（一种源自 Google Borg 系统的数据配置语言）保证可扩展性，运行在 Kubernetes 持续进行控制循环。这使得你可以自由的根据需求场景来设计和选用交付工作流中的每一个步骤，满足业务快速增长的需求，同时持续保证生产环境面向终态的稳定性。
|
||||
KubeVela 的整个交付模型完全是由用户声明式驱动的，兼顾用户体验和健壮性，其控制循环能够有效避免配置漂移，且具备多租权限控制能力。用户可以通过 [CUE 语言](https://cuelang.org/)（一种源自 Google Borg 系统的数据配置语言）自由的根据需求场景来设计和选用交付工作流中的每一个步骤，满足业务快速增长的需求，同时持续保证生产环境面向终态的稳定性。
|
||||
|
||||
- **多集群/混合云应用交付控制平面**
|
||||
|
||||
KubeVela 原生支持丰富的多集群/混合环境持续交付策略，也支持跨环境交付。它既可作为统一的持续交付控制平面增强现有 CI/CD 流水线，也可以满足现代 GitOps 应用交付的趋势与要求，以基础设施即代码（IaC）的方式来驱动持续交付过程。
|
||||
KubeVela 原生支持丰富的多集群/混合环境持续交付策略，也支持跨环境交付。这些交付策略为你的分布式交付流程提供了充足的效率和安全的保证。KubeVela 提供的中心化管控能力也减轻了到每一个集群去排查问题的负担，针对不同的平台提供统一的体验，为了享受自动化交付的便利，你再也不需要成为 Kubernetes 专家。
|
||||
|
||||
|
||||
## KubeVela 与其他软件形态对比
|
||||
|
|
@ -46,10 +46,10 @@ KubeVela 是一个工作在 CI 流程下游的 CD 控制平面（Continuous Deli
|
|||
|
||||
### KubeVela vs. GitOps ( 如 ArgoCD，FluxCD 等)
|
||||
|
||||
KubeVela 并不会替换你的 GitOps 流程，它帮助你在这之上构建一个统一的控制平面，以便增强 GitOps 的能力。
|
||||
KubeVela 可以基于你的 GitOps 流程，并在此之上增加跨云、跨环境的能力：
|
||||
|
||||
* KubeVela 提供跨集群、跨云、跨环境交付的能力，它在单集群会采用诸如 FluxCD 这样的 GitOps 工具作为驱动。
|
||||
* KubeVela 提供了一层用户友好的交付模型，这使得你不会被锁定，你可以灵活切换、扩展底层的实现而不需要改变上层的应用制品。
|
||||
* KubeVela 具有一个用户友好且可编程的工作流，可以让你集成现有的交付工具，包括通知和审批体系。
|
||||
* KubeVela 可以为你提供跨环境交付能力，让你在一个应用中描述多集群的差异化配置并统一的查看状态。
|
||||
|
||||
### KubeVela vs. PaaS 平台 ( 如 Heroku，Cloud Foundry 等 )
|
||||
|
||||
|
|
|
|||
|
|
@ -22,7 +22,7 @@ KubeVela 支持面向应用组织多个 Kubernetes 资源进行交付，常见
|
|||
|
||||
[交付目标(Target)](../getting-started/core-concept#交付目标（target）) 定义了应用交付的运行时集群和命名空间，创建交付目标的同时完成运行时集群的命名空间创建。
|
||||
|
||||
点击 `New Target` 按钮进入创建流程，填写必要的信息，选择集群、命名空间即可完成创建。我们使用 2 个集群来创建交付目标，当然如果你暂无多个集群，也可以使用一个集群的多个命名空间来创建多个交付目标。我们最少准备 3 个交付目标，1 个用于测试环境，2 个或更多用户生产环境。
|
||||
点击 `New Target` 按钮进入创建流程，填写必要的信息，选择集群、命名空间即可完成创建。我们使用 2 个集群来创建交付目标，当然如果你暂无多个集群，也可以使用一个集群的多个命名空间来创建多个交付目标。我们最少准备 3 个交付目标，1 个用于测试环境，2 个或更多用于生产环境。
|
||||
|
||||
## 创建 Kubernetes 应用
|
||||
|
||||
|
|
|
|||
|
|
@ -22,7 +22,7 @@ KubeVela 支持面向应用组织多个 Kubernetes 资源进行交付，常见
|
|||
|
||||
[交付目标(Target)](../getting-started/core-concept#交付目标（target）) 定义了应用交付的运行时集群和命名空间，创建交付目标的同时完成运行时集群的命名空间创建。
|
||||
|
||||
点击 `New Target` 按钮进入创建流程，填写必要的信息，选择集群、命名空间即可完成创建。我们使用 2 个集群来创建交付目标，当然如果你暂无多个集群，也可以使用一个集群的多个命名空间来创建多个交付目标。我们最少准备 3 个交付目标，1 个用于测试环境，2 个或更多用户生产环境。
|
||||
点击 `New Target` 按钮进入创建流程，填写必要的信息，选择集群、命名空间即可完成创建。我们使用 2 个集群来创建交付目标，当然如果你暂无多个集群，也可以使用一个集群的多个命名空间来创建多个交付目标。我们最少准备 3 个交付目标，1 个用于测试环境，2 个或更多用于生产环境。
|
||||
|
||||
## 创建 Kubernetes 应用
|
||||
|
||||
|
|
|
|||
|
|
@ -27,11 +27,11 @@ KubeVela 是一个开箱即用的现代化应用交付与管理平台，它使
|
|||
|
||||
- **声明式交付工作流**
|
||||
|
||||
KubeVela 的整个交付模型完全是由用户声明式驱动的，兼顾用户体验和健壮性。实现层通过 [CUE 语言](https://cuelang.org/)（一种源自 Google Borg 系统的数据配置语言）保证可扩展性，运行在 Kubernetes 持续进行控制循环。这使得你可以自由的根据需求场景来设计和选用交付工作流中的每一个步骤，满足业务快速增长的需求，同时持续保证生产环境面向终态的稳定性。
|
||||
KubeVela 的整个交付模型完全是由用户声明式驱动的，兼顾用户体验和健壮性，其控制循环能够有效避免配置漂移，且具备多租权限控制能力。用户可以通过 [CUE 语言](https://cuelang.org/)（一种源自 Google Borg 系统的数据配置语言）自由的根据需求场景来设计和选用交付工作流中的每一个步骤，满足业务快速增长的需求，同时持续保证生产环境面向终态的稳定性。
|
||||
|
||||
- **多集群/混合云应用交付控制平面**
|
||||
|
||||
KubeVela 原生支持丰富的多集群/混合环境持续交付策略，也支持跨环境交付。它既可作为统一的持续交付控制平面增强现有 CI/CD 流水线，也可以满足现代 GitOps 应用交付的趋势与要求，以基础设施即代码（IaC）的方式来驱动持续交付过程。
|
||||
KubeVela 原生支持丰富的多集群/混合环境持续交付策略，也支持跨环境交付。这些交付策略为你的分布式交付流程提供了充足的效率和安全的保证。KubeVela 提供的中心化管控能力也减轻了到每一个集群去排查问题的负担，针对不同的平台提供统一的体验，为了享受自动化交付的便利，你再也不需要成为 Kubernetes 专家。
|
||||
|
||||
|
||||
## KubeVela 与其他软件形态对比
|
||||
|
|
@ -46,10 +46,10 @@ KubeVela 是一个工作在 CI 流程下游的 CD 控制平面（Continuous Deli
|
|||
|
||||
### KubeVela vs. GitOps ( 如 ArgoCD，FluxCD 等)
|
||||
|
||||
KubeVela 并不会替换你的 GitOps 流程，它帮助你在这之上构建一个统一的控制平面，以便增强 GitOps 的能力。
|
||||
KubeVela 可以基于你的 GitOps 流程，并在此之上增加跨云、跨环境的能力：
|
||||
|
||||
* KubeVela 提供跨集群、跨云、跨环境交付的能力，它在单集群会采用诸如 FluxCD 这样的 GitOps 工具作为驱动。
|
||||
* KubeVela 提供了一层用户友好的交付模型，这使得你不会被锁定，你可以灵活切换、扩展底层的实现而不需要改变上层的应用制品。
|
||||
* KubeVela 具有一个用户友好且可编程的工作流，可以让你集成现有的交付工具，包括通知和审批体系。
|
||||
* KubeVela 可以为你提供跨环境交付能力，让你在一个应用中描述多集群的差异化配置并统一的查看状态。
|
||||
|
||||
### KubeVela vs. PaaS 平台 ( 如 Heroku，Cloud Foundry 等 )
|
||||
|
||||
|
|
|
|||
|
|
@ -22,7 +22,7 @@ KubeVela 支持面向应用组织多个 Kubernetes 资源进行交付，常见
|
|||
|
||||
[交付目标(Target)](../getting-started/core-concept#交付目标（target）) 定义了应用交付的运行时集群和命名空间，创建交付目标的同时完成运行时集群的命名空间创建。
|
||||
|
||||
点击 `New Target` 按钮进入创建流程，填写必要的信息，选择集群、命名空间即可完成创建。我们使用 2 个集群来创建交付目标，当然如果你暂无多个集群，也可以使用一个集群的多个命名空间来创建多个交付目标。我们最少准备 3 个交付目标，1 个用于测试环境，2 个或更多用户生产环境。
|
||||
点击 `New Target` 按钮进入创建流程，填写必要的信息，选择集群、命名空间即可完成创建。我们使用 2 个集群来创建交付目标，当然如果你暂无多个集群，也可以使用一个集群的多个命名空间来创建多个交付目标。我们最少准备 3 个交付目标，1 个用于测试环境，2 个或更多用于生产环境。
|
||||
|
||||
## 创建 Kubernetes 应用
|
||||
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ import Translate, { translate } from '@docusaurus/Translate';
|
|||
|
||||
const features = [
|
||||
{
|
||||
title: <><Translate>Unified Application Delivery Model</Translate></>,
|
||||
title: <><Translate>Unified Application Delivery Experience</Translate></>,
|
||||
imgUrl: 'img/application-centric.svg',
|
||||
description: (
|
||||
<>
|
||||
|
|
@ -16,13 +16,13 @@ const features = [
|
|||
),
|
||||
},
|
||||
{
|
||||
title: <><Translate>Intention-driven Delivery Workflow</Translate></>,
|
||||
title: <><Translate>Automated Deployment across Clusters</Translate></>,
|
||||
imgUrl: 'img/extending-natively.svg',
|
||||
description: (
|
||||
<>
|
||||
<p>
|
||||
<Translate>
|
||||
The whole delivery model was fully intention-driven, having both user experience and robustness. The implementation is driven by CUE - a powerful configuration language developed at Google, and runs on Kubernetes with reconciliation loops. This allows you to design application deployment steps per needs, satisfy the fast growth of businesses requirements, while also keep your production safe with continuous enforcement.
|
||||
KubeVela natively supports rich continuous delivery strategies in various multi-cluster/hybrid-cloud scenarios or mixed environments. These strategies provides efficiency and safety to the distributed delivery process. The centralized management reduces the burden of looking over each clusters and gives unified experience across platforms. With KubeVela, you don't need to have any Ph.D. degree in Kubernetes to run automatic deployments.
|
||||
</Translate>
|
||||
</p>
|
||||
</>
|
||||
|
|
@ -30,13 +30,13 @@ const features = [
|
|||
reverse: true,
|
||||
},
|
||||
{
|
||||
title: <><Translate>Multi-cluster/Hybrid-cloud Continuous Delivery Control Plane</Translate></>,
|
||||
title: <><Translate>Declarative and Highly Extensible Workflow</Translate></>,
|
||||
imgUrl: 'img/simple-yet-extensible-abstraction-mechanism.svg',
|
||||
description: (
|
||||
<>
|
||||
<p>
|
||||
<Translate>
|
||||
KubeVela natively supports rich continuous delivery policies in various multi-cluster/hybrid-cloud scenarios or mixed environments, it supports cross-environment promotion as well. It can enhance the CI/CD pipeline by serving as unified control plane, while it is also capable of leveraging GitOps to automate continuous delivery process in the style of IaC.
|
||||
The application delivery process is driven by declarative workflow. Executed by reconciliation loops with limited privileges, the workflow is both robust and secure enough to prevent any unexpected configuration drifts. Users can also make arbitrary reusable customizations to the workflow through writing CUE definitions. The extensibility will always satisfy your growing business demands while keeping your production safe with continuous enforcement.
|
||||
</Translate>
|
||||
</p>
|
||||
</>
|
||||
|
|
|
|||
|
|
@ -309,7 +309,7 @@ z ?:float
|
|||
```
|
||||
|
||||
Optional variables can be skipped, that usually works together with conditional logic.
|
||||
Specifically, if some field does not exit, the CUE grammar is `if _variable_ != _|_`, the example is like below:
|
||||
Specifically, if some field does not exist, the CUE grammar is `if _variable_ != _|_`, the example is like below:
|
||||
|
||||
```
|
||||
parameter: {
|
||||
|
|
|
|||
|
|
@ -325,7 +325,7 @@ z ?:float
|
|||
```
|
||||
|
||||
Optional variables can be skipped, that usually works together with conditional logic.
|
||||
Specifically, if some field does not exit, the CUE grammar is `if _variable_ != _|_`, the example is like below:
|
||||
Specifically, if some field does not exist, the CUE grammar is `if _variable_ != _|_`, the example is like below:
|
||||
|
||||
```
|
||||
parameter: {
|
||||
|
|
|
|||
|
|
@ -325,7 +325,7 @@ z ?:float
|
|||
```
|
||||
|
||||
Optional variables can be skipped, that usually works together with conditional logic.
|
||||
Specifically, if some field does not exit, the CUE grammar is `if _variable_ != _|_`, the example is like below:
|
||||
Specifically, if some field does not exist, the CUE grammar is `if _variable_ != _|_`, the example is like below:
|
||||
|
||||
```
|
||||
parameter: {
|
||||
|
|
|
|||
|
|
@ -7,24 +7,24 @@ slug: /
|
|||
|
||||
KubeVela is a modern software delivery platform that makes it easier and faster to deliver and manage applications across hybrid, multi-cloud environments.
|
||||
|
||||
Using KubeVela, software teams can build cloud native applications per needs as they grow, then run them anywhere.
|
||||
Using KubeVela, software teams can build cloud native applications per needs as they grow, then deliver them anywhere.
|
||||
|
||||
|
||||
|
||||
|
||||
## Key Features
|
||||
|
||||
* **Unified Application Delivery Model**
|
||||
* **Unified Application Delivery Experience**
|
||||
|
||||
KubeVela introduces a [unified and cross-platform delivery model(OAM)](https://oam.dev/) that allows you to deploy any workload type, including containers, databases, or even VM instances to any cloud or Kubernetes clusters. It helps you to just write application once, and deliver it the same everywhere, no more re-writing everything from scratch for any new delivery target.
|
||||
|
||||
* **Intention-driven Delivery Workflow**
|
||||
* **Automated Deployment across Clusters**
|
||||
|
||||
The whole delivery model was fully intention-driven, having both user experience and robustness. The implementation is driven by CUE - a powerful configuration language developed at Google, and runs on Kubernetes with reconciliation loops. This allows you to design application deployment steps per needs, satisfy the fast growth of businesses requirements, while also keep your production safe with continuous enforcement.
|
||||
KubeVela natively supports rich continuous delivery strategies in various multi-cluster/hybrid-cloud scenarios or mixed environments. These strategies provides efficiency and safety to the distributed delivery process. The centralized management reduces the burden of looking over each clusters and gives unified experience across platforms. With KubeVela, you don't need to have any Ph.D. degree in Kubernetes to run automatic deployments.
|
||||
|
||||
* **Declarative and Highly Extensible Workflow**
|
||||
|
||||
* **Multi-cluster/Hybrid-cloud Continuous Delivery Control Plane**
|
||||
|
||||
KubeVela natively supports rich continuous delivery policies in various multi-cluster/hybrid-cloud scenarios or mixed environments, it supports cross-environment promotion as well. It can enhance the CI/CD pipeline by serving as unified control plane, while it is also capable of leveraging GitOps to automate continuous delivery process in the style of IaC.
|
||||
The application delivery process is driven by declarative workflow. Executed by reconciliation loops with limited privileges, the workflow is both robust and secure enough to prevent any unexpected configuration drifts. Users can also make arbitrary reusable customizations to the workflow through writing CUE definitions. The extensibility will always satisfy your growing business demands while keeping your production safe with continuous enforcement at the same time.
|
||||
|
||||
|
||||
## KubeVela vs. Other Software
|
||||
|
|
@ -37,10 +37,10 @@ KubeVela is a continuous delivery platform that works at downstream of your CI p
|
|||
|
||||
### KubeVela vs. GitOps (ArgoCD, FluxCD, etc.)
|
||||
|
||||
KubeVela does not replace your GitOps process: it improves it by adding a unified control plane on top of it.
|
||||
KubeVela adopts your GitOps process and improves it by adding multi-cluster/hybrid-cloud capabilities:
|
||||
|
||||
* KubeVela can provide cross-environment promotion for your multi-cluster/hybrid-cloud applications, it adopts major of your existing tools for the underlying GitOps driver.
|
||||
* KubeVela has a user-friendly delivery model that _reduces any lock-in_, you can change any underlying tools without rewriting all your application.
|
||||
* KubeVela has a user-friendly and programable workflow that allows you to integrate any of your delivery steps, including approval and notification flows.
|
||||
* With the help of the workflow, KubeVela can provide cross-environment promotion for your multi-cluster/hybrid-cloud applications.
|
||||
|
||||
|
||||
### KubeVela vs. PaaS (Heroku, Cloud Foundry, etc.)
|
||||
|
|
|
|||
|
|
@ -325,7 +325,7 @@ z ?:float
|
|||
```
|
||||
|
||||
Optional variables can be skipped, that usually works together with conditional logic.
|
||||
Specifically, if some field does not exit, the CUE grammar is `if _variable_ != _|_`, the example is like below:
|
||||
Specifically, if some field does not exist, the CUE grammar is `if _variable_ != _|_`, the example is like below:
|
||||
|
||||
```
|
||||
parameter: {
|
||||
|
|
|
|||
Loading…
Reference in New Issue