Chore: make the kubevela.net to be deprecated
Signed-off-by: 悦达 <zengqingguo.zqg@alibaba-inc.com>
This commit is contained in:
悦达
parent
b5e0bfafab
commit
f06d28e815
|
|
@ -63,7 +63,7 @@ git clone https://github.com/openyurtio/yurt-app-managercd yurt-app-manager && h
|
|||
Install the Vela command-line tool and install KubeVela in the cluster:
|
||||
|
||||
```shell
|
||||
curl -fsSl https://kubevela.net/script/install.sh | bash
|
||||
curl -fsSl https://kubevela.io/script/install.sh | bash
|
||||
vela install
|
||||
```
|
||||
We want to reuse the mature Helm charts provided by the community, so we use Helm-type components to install the Nginx Ingress Controller. In KubeVela with microkernel design, Helm components are provided by the FluxCD addon. The following enables the [FluxCD addon](https://kubevela.net/zh/docs/reference/addons/fluxcd).
|
||||
|
|
|
|||
|
|
@ -55,7 +55,7 @@ cd yurt-app-manager && helm install yurt-app-manager -n kube-system ./charts/yur
|
|||
|
||||
安装 Vela 命令行工具，并在集群中安装 KubeVela。
|
||||
```yaml
|
||||
curl -fsSl https://kubevela.net/script/install.sh | bash
|
||||
curl -fsSl https://kubevela.io/script/install.sh | bash
|
||||
vela install
|
||||
```
|
||||
在本案例中，为了复用社区提供的成熟的 Helm Chart，我们用 Helm 类型的组件来安装 Nginx Ingress Controller。在微内核设计的 KubeVela 中，Helm 类型的组件是由 FluxCD 插件提供的，下面启用 [FluxCD 插件](https://kubevela.net/zh/docs/reference/addons/fluxcd)。
|
||||
|
|
|
|||
|
|
@ -35,13 +35,13 @@ KubeVela CLI 提供了常用的集群和应用管理能力。
|
|||
** MacOS/Linux **
|
||||
|
||||
```shell script
|
||||
curl -fsSl https://kubevela.net/script/install.sh | bash
|
||||
curl -fsSl https://kubevela.io/script/install.sh | bash
|
||||
```
|
||||
|
||||
**Windows**
|
||||
|
||||
```shell script
|
||||
powershell -Command "iwr -useb https://kubevela.net/script/install.ps1 | iex"
|
||||
powershell -Command "iwr -useb https://kubevela.io/script/install.ps1 | iex"
|
||||
```
|
||||
|
||||
</TabItem>
|
||||
|
|
|
|||
|
|
@ -41,7 +41,7 @@ helm upgrade -n vela-system --install kubevela kubevela/vela-core --version 1.7.
|
|||
你可以执行下列脚本修复：
|
||||
|
||||
```
|
||||
curl -fsSl https://kubevela.net/script/checklegacy.sh | bash
|
||||
curl -fsSl https://kubevela.io/script/checklegacy.sh | bash
|
||||
```
|
||||
|
||||
这个脚本就是在帮你自动添加 Helm 的注解，你也可以通过如下命令手动修复：
|
||||
|
|
|
|||
|
|
@ -35,13 +35,13 @@ KubeVela CLI 提供了常用的集群和应用管理能力。
|
|||
** MacOS/Linux **
|
||||
|
||||
```shell script
|
||||
curl -fsSl https://kubevela.net/script/install.sh | bash
|
||||
curl -fsSl https://kubevela.io/script/install.sh | bash
|
||||
```
|
||||
|
||||
**Windows**
|
||||
|
||||
```shell script
|
||||
powershell -Command "iwr -useb https://kubevela.net/script/install.ps1 | iex"
|
||||
powershell -Command "iwr -useb https://kubevela.io/script/install.ps1 | iex"
|
||||
```
|
||||
|
||||
</TabItem>
|
||||
|
|
|
|||
|
|
@ -41,7 +41,7 @@ helm upgrade -n vela-system --install kubevela kubevela/vela-core --version 1.7.
|
|||
你可以执行下列脚本修复：
|
||||
|
||||
```
|
||||
curl -fsSl https://kubevela.net/script/checklegacy.sh | bash
|
||||
curl -fsSl https://kubevela.io/script/checklegacy.sh | bash
|
||||
```
|
||||
|
||||
这个脚本就是在帮你自动添加 Helm 的注解，你也可以通过如下命令手动修复：
|
||||
|
|
|
|||
|
|
@ -36,7 +36,7 @@ KubeVela CLI provides an easy way to engage and manage your application delivery
|
|||
** MacOS/Linux **
|
||||
|
||||
```shell script
|
||||
curl -fsSl https://kubevela.net/script/install.sh | bash -s v1.7.7
|
||||
curl -fsSl https://kubevela.io/script/install.sh | bash -s v1.7.7
|
||||
```
|
||||
|
||||
**Windows**
|
||||
|
|
@ -46,7 +46,7 @@ Only the official release version is supported.
|
|||
:::
|
||||
|
||||
```shell script
|
||||
powershell -Command "iwr -useb https://kubevela.net/script/install.ps1 | iex"
|
||||
powershell -Command "iwr -useb https://kubevela.io/script/install.ps1 | iex"
|
||||
```
|
||||
|
||||
</TabItem>
|
||||
|
|
|
|||
|
|
@ -43,7 +43,7 @@ Since we have migrated some workflow step definitions and views from workflow ad
|
|||
You can execute this script to solve it before upgrade helm chart:
|
||||
|
||||
```
|
||||
curl -fsSl https://kubevela.net/script/checklegacy.sh | bash
|
||||
curl -fsSl https://kubevela.io/script/checklegacy.sh | bash
|
||||
```
|
||||
|
||||
The script will just help patch helm annotations for you, you can also do that manually one by one like:
|
||||
|
|
|
|||
|
|
@ -35,7 +35,7 @@ Image Hub | "hub.kubevela.net" | "docker.io" or "ghcr.io/kubevela"
|
|||
Helm charts | https://charts.kubevela.net/core | https://kubevela.github.io/charts
|
||||
Official Addon Registry | https://addons.kubevela.net | https://kubevela.github.io/catalog/official
|
||||
Experimental Addon Registry | - | https://kubevela.github.io/catalog/experimental
|
||||
CLI | https://kubevela.net/script/install.sh | download from [release page](https://github.com/kubevela/kubevela/releases)
|
||||
CLI | https://kubevela.io/script/install.sh | download from [release page](https://github.com/kubevela/kubevela/releases)
|
||||
VelaD | - | migrating
|
||||
|
||||
### You have reached rate limit for Docker Image Registry
|
||||
|
|
|
|||
|
|
@ -36,7 +36,7 @@ KubeVela CLI provides an easy way to engage and manage your application delivery
|
|||
** MacOS/Linux **
|
||||
|
||||
```shell script
|
||||
curl -fsSl https://kubevela.net/script/install.sh | bash -s v1.8.0
|
||||
curl -fsSl https://kubevela.io/script/install.sh | bash -s v1.8.0
|
||||
```
|
||||
|
||||
**Windows**
|
||||
|
|
@ -46,7 +46,7 @@ Only the official release version is supported.
|
|||
:::
|
||||
|
||||
```shell script
|
||||
powershell -Command "iwr -useb https://kubevela.net/script/install.ps1 | iex"
|
||||
powershell -Command "iwr -useb https://kubevela.io/script/install.ps1 | iex"
|
||||
```
|
||||
|
||||
</TabItem>
|
||||
|
|
|
|||
|
|
@ -55,7 +55,7 @@ Since we have migrated some workflow step definitions and views from workflow ad
|
|||
You can execute this script to solve it before upgrade helm chart:
|
||||
|
||||
```
|
||||
curl -fsSl https://kubevela.net/script/checklegacy.sh | bash
|
||||
curl -fsSl https://kubevela.io/script/checklegacy.sh | bash
|
||||
```
|
||||
|
||||
The script will just help patch helm annotations for you, you can also do that manually one by one like:
|
||||
|
|
|
|||
Loading…
Reference in New Issue