Chore: update sidebar and add air-gapped installion for addon
Signed-off-by: Jianbo Sun <jianbo.sjb@alibaba-inc.com>
This commit is contained in:
Jianbo Sun
parent
457629dfde
commit
1c7764e9d7
|
|
@ -2,13 +2,20 @@
|
|||
title: Introduction
|
||||
---
|
||||
|
||||
The developer guide including two parts:
|
||||
|
||||
1. The first part is [contribution guide](#contribution-guide) that introduces how to participate and contribute to the community.
|
||||
2. The second part is [extension guide](#extension-guide) that introduces how to extend KubeVela, you are also very welcome to contribute your extension to the community.
|
||||
|
||||
## Contribution Guide
|
||||
|
||||
KubeVela project is initialized and maintained by the cloud native community since day 0 with [bootstrapping contributors from 8+ different organizations](https://github.com/kubevela/community/blob/main/OWNERS.md#bootstrap-contributors). We intend for KubeVela to have an open governance since the very beginning and donate the project to neutral foundation as soon as it's released.
|
||||
|
||||
To help us create a safe and positive community experience for all, we require all participants adhere to the CNCF Community [Code of Conduct](https://github.com/cncf/foundation/blob/main/code-of-conduct.md).
|
||||
|
||||
This document is a guide to help you through the process of contributing to KubeVela.
|
||||
This part is a guide to help you through the process of contributing to KubeVela.
|
||||
|
||||
## Become a contributor
|
||||
### Become a contributor
|
||||
|
||||
You can contribute to KubeVela in several ways including code and non-code contributions,
|
||||
we appreciate every effort you contribute to the community. Here are some examples:
|
||||
|
|
@ -34,18 +41,32 @@ Unsure where to begin contributing to KubeVela codebase? Start by browsing issue
|
|||
|
||||
Learn the [Release Process And Cadence](./release-process) to know when your code changes will be released.
|
||||
|
||||
|
||||
## Become a community member
|
||||
### Become a community member
|
||||
|
||||
If you're interested to become a community member or learn more about the governance, please check the [community membership](https://github.com/kubevela/community/blob/main/community-membership.md) for details.
|
||||
|
||||
### Contribute to other community projects
|
||||
|
||||
## Contribute Addons and related projects
|
||||
|
||||
* [Build Your Own Addon](../platform-engineers/addon/intro)
|
||||
* [Addon Repository](https://github.com/kubevela/catalog)
|
||||
* [VelaUX Developer Guide](https://github.com/kubevela/velaux/blob/main/CONTRIBUTING.md)
|
||||
* [Terraform Controller Developer Guide](https://github.com/oam-dev/terraform-controller/blob/master/CONTRIBUTING.md)
|
||||
|
||||
|
||||
## Extension Guide
|
||||
|
||||
This part is a guide to help you extend capabilities for KubeVela. Make sure you have already understand the [**core concepts**](../getting-started/core-concept) before you start.
|
||||
|
||||
### Learn CUE with KubeVela
|
||||
|
||||
KubeVela use CUE as it's core engine, and you can use CUE and CRD controller to glue almost every infrastructure capabilities.
|
||||
|
||||
- [Learn CUE in KubeVela](../platform-engineers/cue/basic)
|
||||
- Learn what is [CRD Controller](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/) in Kubernetes
|
||||
|
||||
### Extend Addons
|
||||
|
||||
Building or installing addons is the most important way to extend KubeVela, there's a growing [catalog](https://github.com/kubevela/catalog) of addons you can choose for installation.
|
||||
|
||||
* [Build Your Own Addon](../platform-engineers/addon/intro)
|
||||
* [Extend Cloud Resources by Addon](../platform-engineers/addon/terraform)
|
||||
|
||||
Enjoy coding and collaboration in OSS world!
|
||||
|
|
|
|||
|
|
@ -1,10 +0,0 @@
|
|||
|
||||
# KubeVela Dashboard (WIP)
|
||||
|
||||
KubeVela has a simple client side dashboard for you to interact with. The functionality is equivalent to the vela cli.
|
||||
|
||||
```bash
|
||||
$ vela dashboard
|
||||
```
|
||||
|
||||
> NOTE: this feature is still under development.
|
||||
|
|
@ -12,9 +12,8 @@ KubeVela is programmable, you have the following ways to discover and extend the
|
|||
|
||||
* Get more capabilities from [installing addons](../../how-to/cli/addon/addon), you can refer to [the overview of official addons](../../reference/addons/overview) for more details.
|
||||
|
||||
* Extend KubeVela by yourself
|
||||
* Develop and Extend KubeVela by yourself
|
||||
- Read the [developer guide](../../contributor/overview) to learn how to contribute and extend capabilities for KubeVela.
|
||||
- KubeVela use CUE as it's core engine, [learn CUE in KubeVela](../../platform-engineers/cue/basic) and try to extend with CUE configurations.
|
||||
- [Building your own addons](../../platform-engineers/addon/intro) for extension, you can also [extend cloud resources by addon](../../platform-engineers/addon/terraform).
|
||||
|
||||
* Read [how to build definitions](../../platform-engineers/cue/definition-edit) to build your own capability from existing ones.
|
||||
* [Build your own capability from scratch](../../platform-engineers/cue/advanced)
|
||||
and learn more features about how to [define custom components](../../platform-engineers/components/custom-component).
|
||||
* [Build your own addons](../../platform-engineers/addon/intro).
|
||||
|
|
|
|||
|
|
@ -108,7 +108,7 @@ $ vela addon registry delete experimental
|
|||
Successfully delete an addon registry experimental
|
||||
```
|
||||
|
||||
### Enable Addon offline
|
||||
### Air-Gapped Installation for Addon
|
||||
|
||||
For some reason, if your cluster network cannot request the official addon registry you can enable an addon with a local dir. eg:
|
||||
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: Custom installation and upgrade
|
||||
title: Custom Installation/Upgrade
|
||||
---
|
||||
|
||||
import Tabs from '@theme/Tabs';
|
||||
|
|
|
|||
|
|
@ -1,27 +1,27 @@
|
|||
---
|
||||
title: Enable Addon without Internet Access
|
||||
title: Air-gapped Installation for Addon
|
||||
---
|
||||
|
||||
## Enable without Internet
|
||||
If your environments don't have network access to `https://addons.kubevela.net` or `https://github.com/kubevela/catalog`, this guide will demonstrate how to install in the air-gapped environment.
|
||||
|
||||
If your environments don't have access to `https://addons.kubevela.net` or `https://github.com/kubevela/catalog`, you should git clone the repo `https://github.com/kubevela/catalog/tree/master/addons` locally. You can specify a local addon directory when enable an addon for installation.
|
||||
Before installing an addon, you should check if the addon contains any container images or other sub helm charts in it. If so, the addon also can't be installed well. You can follow these steps to make it success.
|
||||
Generally, you should git clone the repo which contained the addon configuration, you can specify a local addon directory when enable an addon for installation. While you should make sure all container images or helm charts are replaced by your private registry.
|
||||
|
||||
1. Git clone [the catalog repo](https://github.com/kubevela/catalog) to download these addon files.You can find all official addons in subdirectory `./addons/` and experimental addons in subdirectory `./experimental/addons`.
|
||||
You can follow these steps as an example.
|
||||
|
||||
1. Git clone [the catalog repo](https://github.com/kubevela/catalog) to download these addon files. You can find all official addons in subdirectory `./addons/` and experimental addons in subdirectory `./experimental/addons`.
|
||||
|
||||
```yaml
|
||||
git clone https://github.com/kubevela/catalog
|
||||
```
|
||||
|
||||
2. Sync the container images relied on by addon to your own image repository.
|
||||
For example, you want sync the image of the helm controller image of fluxcd addon.
|
||||
2. Sync the dependency container images in the addon to your private image registry, the sync command can be as following:
|
||||
|
||||
```yaml
|
||||
$ docker pull fluxcd/helm-controller:v0.11.1
|
||||
$ docker push <your repo url>/fluxcd/helm-controller:v0.11.1
|
||||
```
|
||||
|
||||
3. Parts of addons maybe rely on some helm charts such as terraform addon. You should sync these helm charts to your own chart repository.
|
||||
3. Parts of addons may rely on helm charts, e.g. `terraform addon`. You should sync these helm charts to your private chart registry.
|
||||
|
||||
```yaml
|
||||
$ helm repo add vela-charts https://charts.kubevela.net/addons
|
||||
|
|
@ -30,19 +30,21 @@ $ helm pull vela-charts/terraform-controller --version 0.3.5
|
|||
$ helm push terraform-controller-0.3.5.tgz <your charts repo url>
|
||||
```
|
||||
|
||||
You can read this [docs](https://helm.sh/docs/topics/chart_repository/) to get knowledge how to build your own helm repo.
|
||||
You can read the [helm official docs](https://helm.sh/docs/topics/chart_repository/) to learn more about how to build your own helm registry.
|
||||
|
||||
4. Modify the values of addon by referring to your own image/chart repository. You can find all relied on images/charts in the files of subdirectory `resources/` and modify them.
|
||||
For example, you can modify the fluxcd addon files `addons/fluxcd/resources/deployment/helm-controller.yaml` the deployment object's field `spec.sepc.containers[0].image` to your own image repo.We will introduce what images/helm charts needed to sync for each addon below.
|
||||
4. Modify the values of addon by referring to your own image/chart registry. You can find all images/charts dependency in the files of subdirectory `resources/`, just modify the configuration.
|
||||
For example, you can modify the fluxcd addon files `addons/fluxcd/resources/deployment/helm-controller.yaml` the deployment object's field `spec.sepc.containers[0].image` to your own image repo.
|
||||
|
||||
5. Use `vela cli` to enable an addon with specify a local addon dir to install offline.
|
||||
|
||||
```yaml
|
||||
$ vela addon enable <dir>
|
||||
$ vela addon enable /your/local/addon/directory
|
||||
```
|
||||
|
||||
## Images or helm charts need to sync
|
||||
|
||||
Here's a list about images or helm charts of all official addons that should be synced for air-gapped installation.
|
||||
|
||||
### 1. FluxCD
|
||||
|
||||
You need sync these images to your own image registry, and modify the related addon files to reference you own registry.
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: Version Migration
|
||||
title: Migrate from Old Versions
|
||||
---
|
||||
|
||||
This doc aims to provide a migration guide from old versions to the new ones without disturb the running business. However scenarios are different from each other, we strongly recommend you to test the migration with a simulation environment before real migration for your production.
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: Customize Resource Topology
|
||||
title: Resource Topology
|
||||
---
|
||||
|
||||
The resource topology graph of VelaUX can automatically show the resource tree of an application for any workloads including Helm charts and cloud resources.
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: Customize UX of Definition
|
||||
title: UX of Definition
|
||||
---
|
||||
|
||||
VelaUX uses the UI-Schema specification for the extension of components, workflow steps, and operation and maintenance feature resources, in the case of variable input parameters, to achieve a more native UI experience.
|
||||
|
|
|
|||
|
|
@ -196,6 +196,7 @@ spec:
|
|||
conflictsWith:
|
||||
- <与该运维特征冲突的其他运维特征名称>
|
||||
revisionEnabled: <运维能力是否感知组件版本的变化>
|
||||
controlPlaneOnly: <运维能力产生的资源是否部署到管控集群>
|
||||
schematic: # 抽象方式
|
||||
cue: # 存在多种抽象方式
|
||||
template: <CUE 格式模板>
|
||||
|
|
@ -212,6 +213,7 @@ spec:
|
|||
* 是否由该运维特征管理工作负载（`.spec.manageWorkload`）,可缺省字段，bool 类型，设置为 true 则标识这个运维特征会负责工作负载的创建、更新、以及资源回收，通常是灰度发布的运维特征会具备这个能力。
|
||||
* 该运维特征是否不计入版本变化的计算（`.spec.skipRevisionAffect`）,可缺省字段，bool 类型，设置为 true 则标识这个运维特征的修改不计入版本的变化，即用户在应用中纯粹修改这个运维特征的字段不会触发应用本身的版本变化。
|
||||
* 运维能力是否感知组件版本的变化（`.spec.revisionEnabled`）字段，可缺省字段，bool 类型，设置为 true 表示组件会生成的资源后缀会带版本后缀。
|
||||
* 运维能力产生的资源是否部署到管控集群（`.spec.controlPlaneOnly`）字段，可缺省字段，bool 类型，设置为 true 表示 trait 生成的资源会被部署到管控集群，即`local`
|
||||
|
||||
|
||||
让我们来看一个实际的例子：
|
||||
|
|
|
|||
|
|
@ -100,6 +100,7 @@ module.exports = {
|
|||
'platform-engineers/system-operation/bootstrap-parameters',
|
||||
'platform-engineers/advanced-install',
|
||||
'platform-engineers/system-operation/vela-cli-image',
|
||||
'platform-engineers/system-operation/enable-addon-offline',
|
||||
'platform-engineers/system-operation/migration-from-old-version'
|
||||
],
|
||||
},
|
||||
|
|
|
|||
|
|
@ -2,13 +2,20 @@
|
|||
title: Introduction
|
||||
---
|
||||
|
||||
The developer guide including two parts:
|
||||
|
||||
1. The first part is [contribution guide](#contribution-guide) that introduces how to participate and contribute to the community.
|
||||
2. The second part is [extension guide](#extension-guide) that introduces how to extend KubeVela, you are also very welcome to contribute your extension to the community.
|
||||
|
||||
## Contribution Guide
|
||||
|
||||
KubeVela project is initialized and maintained by the cloud native community since day 0 with [bootstrapping contributors from 8+ different organizations](https://github.com/kubevela/community/blob/main/OWNERS.md#bootstrap-contributors). We intend for KubeVela to have an open governance since the very beginning and donate the project to neutral foundation as soon as it's released.
|
||||
|
||||
To help us create a safe and positive community experience for all, we require all participants adhere to the CNCF Community [Code of Conduct](https://github.com/cncf/foundation/blob/main/code-of-conduct.md).
|
||||
|
||||
This document is a guide to help you through the process of contributing to KubeVela.
|
||||
This part is a guide to help you through the process of contributing to KubeVela.
|
||||
|
||||
## Become a contributor
|
||||
### Become a contributor
|
||||
|
||||
You can contribute to KubeVela in several ways including code and non-code contributions,
|
||||
we appreciate every effort you contribute to the community. Here are some examples:
|
||||
|
|
@ -34,18 +41,32 @@ Unsure where to begin contributing to KubeVela codebase? Start by browsing issue
|
|||
|
||||
Learn the [Release Process And Cadence](./release-process) to know when your code changes will be released.
|
||||
|
||||
|
||||
## Become a community member
|
||||
### Become a community member
|
||||
|
||||
If you're interested to become a community member or learn more about the governance, please check the [community membership](https://github.com/kubevela/community/blob/main/community-membership.md) for details.
|
||||
|
||||
### Contribute to other community projects
|
||||
|
||||
## Contribute Addons and related projects
|
||||
|
||||
* [Build Your Own Addon](../platform-engineers/addon/intro)
|
||||
* [Addon Repository](https://github.com/kubevela/catalog)
|
||||
* [VelaUX Developer Guide](https://github.com/kubevela/velaux/blob/main/CONTRIBUTING.md)
|
||||
* [Terraform Controller Developer Guide](https://github.com/oam-dev/terraform-controller/blob/master/CONTRIBUTING.md)
|
||||
|
||||
|
||||
## Extension Guide
|
||||
|
||||
This part is a guide to help you extend capabilities for KubeVela. Make sure you have already understand the [**core concepts**](../getting-started/core-concept) before you start.
|
||||
|
||||
### Learn CUE with KubeVela
|
||||
|
||||
KubeVela use CUE as it's core engine, and you can use CUE and CRD controller to glue almost every infrastructure capabilities.
|
||||
|
||||
- [Learn CUE in KubeVela](../platform-engineers/cue/basic)
|
||||
- Learn what is [CRD Controller](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/) in Kubernetes
|
||||
|
||||
### Extend Addons
|
||||
|
||||
Building or installing addons is the most important way to extend KubeVela, there's a growing [catalog](https://github.com/kubevela/catalog) of addons you can choose for installation.
|
||||
|
||||
* [Build Your Own Addon](../platform-engineers/addon/intro)
|
||||
* [Extend Cloud Resources by Addon](../platform-engineers/addon/terraform)
|
||||
|
||||
Enjoy coding and collaboration in OSS world!
|
||||
|
|
|
|||
|
|
@ -1,10 +0,0 @@
|
|||
|
||||
# KubeVela Dashboard (WIP)
|
||||
|
||||
KubeVela has a simple client side dashboard for you to interact with. The functionality is equivalent to the vela cli.
|
||||
|
||||
```bash
|
||||
$ vela dashboard
|
||||
```
|
||||
|
||||
> NOTE: this feature is still under development.
|
||||
|
|
@ -12,9 +12,8 @@ KubeVela is programmable, you have the following ways to discover and extend the
|
|||
|
||||
* Get more capabilities from [installing addons](../../how-to/cli/addon/addon), you can refer to [the overview of official addons](../../reference/addons/overview) for more details.
|
||||
|
||||
* Extend KubeVela by yourself
|
||||
* Develop and Extend KubeVela by yourself
|
||||
- Read the [developer guide](../../contributor/overview) to learn how to contribute and extend capabilities for KubeVela.
|
||||
- KubeVela use CUE as it's core engine, [learn CUE in KubeVela](../../platform-engineers/cue/basic) and try to extend with CUE configurations.
|
||||
- [Building your own addons](../../platform-engineers/addon/intro) for extension, you can also [extend cloud resources by addon](../../platform-engineers/addon/terraform).
|
||||
|
||||
* Read [how to build definitions](../../platform-engineers/cue/definition-edit) to build your own capability from existing ones.
|
||||
* [Build your own capability from scratch](../../platform-engineers/cue/advanced)
|
||||
and learn more features about how to [define custom components](../../platform-engineers/components/custom-component).
|
||||
* [Build your own addons](../../platform-engineers/addon/intro).
|
||||
|
|
|
|||
|
|
@ -108,7 +108,7 @@ $ vela addon registry delete experimental
|
|||
Successfully delete an addon registry experimental
|
||||
```
|
||||
|
||||
### Enable Addon offline
|
||||
### Air-Gapped Installation for Addon
|
||||
|
||||
For some reason, if your cluster network cannot request the official addon registry you can enable an addon with a local dir. eg:
|
||||
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: Custom installation and upgrade
|
||||
title: Custom Installation/Upgrade
|
||||
---
|
||||
|
||||
import Tabs from '@theme/Tabs';
|
||||
|
|
|
|||
|
|
@ -162,6 +162,7 @@ spec:
|
|||
conflictsWith:
|
||||
- <other Traits that conflict with this><>
|
||||
revisionEnabled: <whether Trait is aware of changes in component version>
|
||||
controlPlaneOnly: <Whether resources generated by trait are dispatched to the hubcluster (local)>
|
||||
schematic: # Abstract
|
||||
cue: # There are many abstracts
|
||||
template: <CUE format template>
|
||||
|
|
|
|||
|
|
@ -1,27 +1,27 @@
|
|||
---
|
||||
title: Enable Addon without Internet Access
|
||||
title: Air-gapped Installation for Addon
|
||||
---
|
||||
|
||||
## Enable without Internet
|
||||
If your environments don't have network access to `https://addons.kubevela.net` or `https://github.com/kubevela/catalog`, this guide will demonstrate how to install in the air-gapped environment.
|
||||
|
||||
If your environments don't have access to `https://addons.kubevela.net` or `https://github.com/kubevela/catalog`, you should git clone the repo `https://github.com/kubevela/catalog/tree/master/addons` locally. You can specify a local addon directory when enable an addon for installation.
|
||||
Before installing an addon, you should check if the addon contains any container images or other sub helm charts in it. If so, the addon also can't be installed well. You can follow these steps to make it success.
|
||||
Generally, you should git clone the repo which contained the addon configuration, you can specify a local addon directory when enable an addon for installation. While you should make sure all container images or helm charts are replaced by your private registry.
|
||||
|
||||
1. Git clone [the catalog repo](https://github.com/kubevela/catalog) to download these addon files.You can find all official addons in subdirectory `./addons/` and experimental addons in subdirectory `./experimental/addons`.
|
||||
You can follow these steps as an example.
|
||||
|
||||
1. Git clone [the catalog repo](https://github.com/kubevela/catalog) to download these addon files. You can find all official addons in subdirectory `./addons/` and experimental addons in subdirectory `./experimental/addons`.
|
||||
|
||||
```yaml
|
||||
git clone https://github.com/kubevela/catalog
|
||||
```
|
||||
|
||||
2. Sync the container images relied on by addon to your own image repository.
|
||||
For example, you want sync the image of the helm controller image of fluxcd addon.
|
||||
2. Sync the dependency container images in the addon to your private image registry, the sync command can be as following:
|
||||
|
||||
```yaml
|
||||
$ docker pull fluxcd/helm-controller:v0.11.1
|
||||
$ docker push <your repo url>/fluxcd/helm-controller:v0.11.1
|
||||
```
|
||||
|
||||
3. Parts of addons maybe rely on some helm charts such as terraform addon. You should sync these helm charts to your own chart repository.
|
||||
3. Parts of addons may rely on helm charts, e.g. `terraform addon`. You should sync these helm charts to your private chart registry.
|
||||
|
||||
```yaml
|
||||
$ helm repo add vela-charts https://charts.kubevela.net/addons
|
||||
|
|
@ -30,19 +30,21 @@ $ helm pull vela-charts/terraform-controller --version 0.3.5
|
|||
$ helm push terraform-controller-0.3.5.tgz <your charts repo url>
|
||||
```
|
||||
|
||||
You can read this [docs](https://helm.sh/docs/topics/chart_repository/) to get knowledge how to build your own helm repo.
|
||||
You can read the [helm official docs](https://helm.sh/docs/topics/chart_repository/) to learn more about how to build your own helm registry.
|
||||
|
||||
4. Modify the values of addon by referring to your own image/chart repository. You can find all relied on images/charts in the files of subdirectory `resources/` and modify them.
|
||||
For example, you can modify the fluxcd addon files `addons/fluxcd/resources/deployment/helm-controller.yaml` the deployment object's field `spec.sepc.containers[0].image` to your own image repo.We will introduce what images/helm charts needed to sync for each addon below.
|
||||
4. Modify the values of addon by referring to your own image/chart registry. You can find all images/charts dependency in the files of subdirectory `resources/`, just modify the configuration.
|
||||
For example, you can modify the fluxcd addon files `addons/fluxcd/resources/deployment/helm-controller.yaml` the deployment object's field `spec.sepc.containers[0].image` to your own image repo.
|
||||
|
||||
5. Use `vela cli` to enable an addon with specify a local addon dir to install offline.
|
||||
|
||||
```yaml
|
||||
$ vela addon enable <dir>
|
||||
$ vela addon enable /your/local/addon/directory
|
||||
```
|
||||
|
||||
## Images or helm charts need to sync
|
||||
|
||||
Here's a list about images or helm charts of all official addons that should be synced for air-gapped installation.
|
||||
|
||||
### 1. FluxCD
|
||||
|
||||
You need sync these images to your own image registry, and modify the related addon files to reference you own registry.
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: Version Migration
|
||||
title: Migrate from Old Versions
|
||||
---
|
||||
|
||||
This doc aims to provide a migration guide from old versions to the new ones without disturb the running business. However scenarios are different from each other, we strongly recommend you to test the migration with a simulation environment before real migration for your production.
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: Customize Resource Topology
|
||||
title: Resource Topology
|
||||
---
|
||||
|
||||
The resource topology graph of VelaUX can automatically show the resource tree of an application for any workloads including Helm charts and cloud resources.
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: Customize UX of Definition
|
||||
title: UX of Definition
|
||||
---
|
||||
|
||||
VelaUX uses the UI-Schema specification for the extension of components, workflow steps, and operation and maintenance feature resources, in the case of variable input parameters, to achieve a more native UI experience.
|
||||
|
|
|
|||
|
|
@ -208,6 +208,10 @@
|
|||
"type": "doc",
|
||||
"id": "version-v1.4/platform-engineers/system-operation/vela-cli-image"
|
||||
},
|
||||
{
|
||||
"type": "doc",
|
||||
"id": "version-v1.4/platform-engineers/system-operation/enable-addon-offline"
|
||||
},
|
||||
{
|
||||
"type": "doc",
|
||||
"id": "version-v1.4/platform-engineers/system-operation/migration-from-old-version"
|
||||
|
|
|
|||
Loading…
Reference in New Issue