Fix invalid link of installing cloud resources links (#469)
* Fix invalid link of installing cloud resources links As the previous link of installing cloud resources in `provision and consume cloud resources` is invalid, fixed it. Also update the wrong file name Signed-off-by: Zheng Xi Zhou <zzxwill@gmail.com> * Update deploy cloud resources in Chinese Signed-off-by: Zheng Xi Zhou <zzxwill@gmail.com>
This commit is contained in:
Zheng Xi Zhou
GitHub
parent
6cfd3fdf87
commit
8dc4311ee9
|
|
@ -13,7 +13,7 @@ You can use cloud resources of various manufacturers in a standardized and unifi
|
|||
|
||||
This tutorial will talk about how to provision and consume Cloud Resources by Terraform.
|
||||
|
||||
> ⚠️ This section requires your platform engineers have already enabled [add-on 'terraform/provider-alicloud'](../../../install#4-optional-enable-addons).
|
||||
> ⚠️ This section requires your platform engineers have already enabled [cloud resources addon](../../../reference/addons/terraform).
|
||||
|
||||
## Supported Cloud Resource list
|
||||
|
||||
|
|
@ -2,9 +2,9 @@
|
|||
title: Extend Cloud Resources
|
||||
---
|
||||
|
||||
To enable end users to [provision and consume cloud resources](../../end-user/components/cloud-services/provider-and-consume-cloud-services),
|
||||
To enable end users to [provision and consume cloud resources](../../end-user/components/cloud-services/provision-and-consume-cloud-services),
|
||||
platform engineers need to prepare ComponentDefinitions for cloud resources if end users' requirements are beyond the
|
||||
[built-in capabilities](../../end-user/components/cloud-services/provider-and-consume-cloud-services#supported-cloud-resource-list).
|
||||
[built-in capabilities](../../end-user/components/cloud-services/provision-and-consume-cloud-services#supported-cloud-resource-list).
|
||||
|
||||
Here is the guide to create Terraform typed ComponentDefinitions of cloud resources for cloud providers Alibaba Cloud, AWS and Azure.
|
||||
|
||||
|
|
@ -157,7 +157,7 @@ $ vela show alibaba-eip
|
|||
```
|
||||
|
||||
If the tables display, the ComponentDefinition should work. To take a step further, you can verify it by provision an actual EIP instance per
|
||||
the doc [Provision cloud resources](../../end-user/components/cloud-services/provider-and-consume-cloud-services#provision-cloud-resources).
|
||||
the doc [Provision cloud resources](../../end-user/components/cloud-services/provision-and-consume-cloud-services#provision-cloud-resources).
|
||||
|
||||
## Generate documentation
|
||||
|
||||
|
|
|
|||
|
|
@ -11,7 +11,7 @@ title: Addon Cloud Resources
|
|||
|
||||
## Terraform Provider addon for Alibaba Cloud
|
||||
|
||||
Enable Terraform Alibaba Cloud Provider as below to [provision and/or consume cloud resources](../../end-user/components/cloud-services/provider-and-consume-cloud-services).
|
||||
Enable Terraform Alibaba Cloud Provider as below to [provision and/or consume cloud resources](../../end-user/components/cloud-services/provision-and-consume-cloud-services).
|
||||
|
||||
Here is how to get [access key](https://help.aliyun.com/knowledge_detail/38738.html). Set the value for `ALICLOUD_REGION` by picking one `RegionId` from [Alibaba Cloud region list](https://www.alibabacloud.com/help/doc-detail/72379.htm).
|
||||
You can also set the value for parameter `ALICLOUD_SECURITY_TOKEN`, which is optional, per [this doc](https://www.alibabacloud.com/help/doc-detail/28756.htm).
|
||||
|
|
@ -22,7 +22,7 @@ title: Addon Cloud Resources
|
|||
|
||||
## Terraform Provider addon for Azure
|
||||
|
||||
Enable Terraform Azure Provider as below to [provision and/or consume cloud resources](../../end-user/components/cloud-services/provider-and-consume-cloud-services).
|
||||
Enable Terraform Azure Provider as below to [provision and/or consume cloud resources](../../end-user/components/cloud-services/provision-and-consume-cloud-services).
|
||||
|
||||
Set these parameters below per [Authenticate Terraform to Azure](https://docs.microsoft.com/en-us/azure/developer/terraform/authenticate-to-azure?tabs=bash).
|
||||
|
||||
|
|
@ -32,7 +32,7 @@ title: Addon Cloud Resources
|
|||
|
||||
## Terraform Provider addon for AWS
|
||||
|
||||
Enable Terraform AWS Provider as below to [provision and/or consume cloud resources](../../end-user/components/cloud-services/provider-and-consume-cloud-services).
|
||||
Enable Terraform AWS Provider as below to [provision and/or consume cloud resources](../../end-user/components/cloud-services/provision-and-consume-cloud-services).
|
||||
|
||||
Set these parameters below per [Authenticate Terraform to AWS](https://registry.terraform.io/providers/hashicorp/aws/latest/docs#environment-variables).
|
||||
|
||||
|
|
|
|||
|
|
@ -25,40 +25,46 @@ First, visit [VelaUX (KubeVela Dashboard)](../install#3-install-velaux), switch
|
|||
- provider-alibaba
|
||||
- provider-aws
|
||||
- provider-azure
|
||||
- provider-tencent
|
||||
|
||||
We can provision cloud resources in Alibaba Cloud, AWS, and Azure respectively.
|
||||
We can provision cloud resources in Alibaba Cloud, AWS, Azure and Tencent Cloud respectively.
|
||||
|
||||
Follow the instructions on all the properties of the addon for each cloud provider to set the addon and enable it.
|
||||
|
||||
For example, for Alibaba Cloud, you need to set the following properties:
|
||||
Then fill in your ALICLOUD_ACCESS_KEY, ALICLOUD_REGION, and ALICLOUD_SECRET_KEY to enable it。
|
||||
|
||||
> Notice: KubeVela encrypts all the keys, hence no need to worry about its safety.
|
||||
|
||||
|
||||
|
||||
Then fill in your ALICLOUD_ACCESS_KEY, ALICLOUD_REGION, and ALICLOUD_SECRET_KEY to enable it。
|
||||
|
||||
The creating process of cloud services pulls configuration from GitHub. If your control plane
|
||||
cluster that runs KubeVela is very hard to connect to GitHub, please open up the `GithubBlocked` option in `terraform`
|
||||
addon.
|
||||
|
||||
KubeVela supports the following types of resources and more later on:
|
||||
|
||||
Cloud Provider | Cloud Resource | Description
|
||||
----------------|------------------------------------------------------| -------------
|
||||
Alibaba Cloud | [ACK](../end-user/components/cloud-services/terraform/alibaba-ack) | Terraform configuration for Alibaba Cloud ACK cluster
|
||||
| | [EIP](../end-user/components/cloud-services/terraform/alibaba-eip) | Terraform configuration for Alibaba Cloud EIP
|
||||
| | [OSS](../end-user/components/cloud-services/terraform/alibaba-oss) | Terraform configuration for Alibaba Cloud OSS
|
||||
| | [RDS](../end-user/components/cloud-services/terraform/alibaba-rds) | Terraform configuration for Alibaba Cloud RDS
|
||||
| | [Redis](../end-user/components/cloud-services/terraform/alibaba-redis) | Terraform configuration for Alibaba Cloud Redis
|
||||
| | [VPC](../end-user/components/cloud-services/terraform/alibaba-vpc) | Terraform configuration for Alibaba Cloud VPC
|
||||
| Azure | [Mariadb](../end-user/components/cloud-services/terraform/azure-database-mariadb) | Terraform configuration for Azure Database Mariadb
|
||||
| | [Storage Account](../end-user/components/cloud-services/terraform/azure-storage-account) | Terraform configuration for Azure Storage Account
|
||||
| AWS | [S3](../end-user/components/cloud-services/terraform/aws-s3) | Terraform configuration for AWS S3 bucket
|
||||
| Orchestration Type | Cloud Provider | Cloud Resource | Description |
|
||||
|--------------------|----------------|------------------------------------------------------------------------------------------|-----------------------------------------------------------------------|
|
||||
| Terraform | Alibaba Cloud | [ACK](../end-user/components/cloud-services/terraform/alibaba-ack) | Terraform configuration for Alibaba Cloud ACK cluster |
|
||||
| | | [ASK](../end-user/components/cloud-services/terraform/alibaba-ask) | Terraform configuration for Alibaba Cloud Serverless Kubernetes (ASK) |
|
||||
| | | [EIP](../end-user/components/cloud-services/terraform/alibaba-eip) | Terraform configuration for Alibaba Cloud EIP |
|
||||
| | | [OSS](../end-user/components/cloud-services/terraform/alibaba-oss) | Terraform configuration for Alibaba Cloud OSS |
|
||||
| | | [RDS](../end-user/components/cloud-services/terraform/alibaba-rds) | Terraform configuration for Alibaba Cloud RDS |
|
||||
| | | [Redis](../end-user/components/cloud-services/terraform/alibaba-redis) | Terraform configuration for Alibaba Cloud Redis |
|
||||
| | | [SLS Project](../end-user/components/cloud-services/terraform/alibaba-sls-project) | Terraform configuration for Alibaba Cloud SLS Project |
|
||||
| | | [SLS Store](../end-user/components/cloud-services/terraform/alibaba-sls-store) | Terraform configuration for Alibaba Cloud SLS Store |
|
||||
| | | [VPC](../end-user/components/cloud-services/terraform/alibaba-vpc) | Terraform configuration for Alibaba Cloud VPC |
|
||||
| | | [VSwitch](../end-user/components/cloud-services/terraform/alibaba-vswitch) | Terraform configuration for Alibaba Cloud VSwitch |
|
||||
| | AWS | [S3](../end-user/components/cloud-services/terraform/aws-s3) | Terraform configuration for AWS S3 bucket |
|
||||
| | Azure | [Mariadb](../end-user/components/cloud-services/terraform/azure-database-mariadb) | Terraform configuration for Azure Database Mariadb |
|
||||
| | | [Storage Account](../end-user/components/cloud-services/terraform/azure-storage-account) | Terraform configuration for Azure Storage Account |
|
||||
|
||||
## Creating your cloud service
|
||||
|
||||
First [create an application](../how-to/dashboard/application/create-application). Please choose the type of your cloud service,
|
||||
which has a prefix of `aws-`, `azure` or `alibaba-`.
|
||||
which has a prefix of `aws-`, `azure`, `alibaba-` or `tencent-`.
|
||||
|
||||
For different vendors, these parameters update accordingly.
|
||||
|
||||
|
|
|
|||
|
|
@ -8,8 +8,7 @@ title: 创建和使用云资源
|
|||
KubeVela 通过云资源组件（Component）和运维特征（Trait）里的资源绑定功能，高效安全地完成不同类型云资源的集成工作。目前你可以直接调用下面这些云资源默认组件。
|
||||
同时在未来，更多新的云资源也会在社区的支撑下逐渐成为默认选项，让你标准化统一地去使用各种厂商的云资源。
|
||||
|
||||
> ⚠️ 请确认管理员已经安装了 [Terraform 插件 'terraform/provider-alicloud'](../../../install#4-【可选】安装插件).
|
||||
|
||||
> ⚠️ 请确认管理员已经安装了 [云资源插件](../../../reference/addons/terraform)。
|
||||
|
||||
## 支持的云资源列表
|
||||
|
||||
|
|
@ -6,7 +6,7 @@ title: 扩展云资源
|
|||
Terraform 是目前业内支持云资源最广泛也最受欢迎的组件，KubeVela 对 Terraform 进行了额外的支持，使得用户可以通过 Kubernetes CRD 的方式配合
|
||||
Terraform 使用任意的云资源。
|
||||
|
||||
为了使最终用户能够[部署和消费云资源](../../end-user/components/cloud-services/provider-and-consume-cloud-services)，当用户的要求超出了 [内置云资源的能力](../../end-user/components/cloud-services/provider-and-consume-cloud-services)，
|
||||
为了使最终用户能够[部署和消费云资源](../../end-user/components/cloud-services/provision-and-consume-cloud-services)，当用户的要求超出了 [内置云资源的能力](../../end-user/components/cloud-services/provision-and-consume-cloud-services)，
|
||||
管理员需要要为云资源准备 ComponentDefinitions。
|
||||
|
||||
以下是为云供应商阿里云、AWS 和 Azure 创建 Terraform 类型的云资源 ComponentDefinitions 的指南。
|
||||
|
|
@ -159,7 +159,7 @@ $ vela show alibaba-eip
|
|||
+-----------+-----------------------------------------------------------------------------+--------+----------+---------+
|
||||
```
|
||||
|
||||
如果表格能正常出来，ComponentDefinition 应该就可以工作了。更进一步，你可以通过文档[部署云资源](../../end-user/components/cloud-services/provider-and-consume-cloud-services)创建一个实际的 EIP 来验证。
|
||||
如果表格能正常出来，ComponentDefinition 应该就可以工作了。更进一步，你可以通过文档[部署云资源](../../end-user/components/cloud-services/provision-and-consume-cloud-services)创建一个实际的 EIP 来验证。
|
||||
|
||||
## 生成文档
|
||||
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@ title: 云资源插件
|
|||
|
||||
## 阿里云 Terraform Provider 插件
|
||||
|
||||
执行如下命令开启 Terraform 对阿里云的支持，可以[创建和消费云资源](../../end-user/components/cloud-services/provider-and-consume-cloud-services)：
|
||||
执行如下命令开启 Terraform 对阿里云的支持，可以[创建和消费云资源](../../end-user/components/cloud-services/provision-and-consume-cloud-services)：
|
||||
|
||||
其中，请参考[如何获取 Access Key](https://help.aliyun.com/knowledge_detail/38738.html)设置 Access Key，参考 [Region 列表](https://www.alibabacloud.com/help/doc-detail/72379.htm) 中的 `RegionId` 设置 `ALICLOUD_REGION`。
|
||||
参数 `ALICLOUD_SECURITY_TOKEN` 是可选的，你可以通过 [这篇介绍](https://www.alibabacloud.com/help/zh/doc-detail/28756.htm) 设置。
|
||||
|
|
@ -20,7 +20,7 @@ title: 云资源插件
|
|||
|
||||
## Azure Terraform Provider 插件
|
||||
|
||||
执行如下命令开启 Terraform 对 Azure 的支持，可以[创建和消费云资源](../../end-user/components/cloud-services/provider-and-consume-cloud-services)：
|
||||
执行如下命令开启 Terraform 对 Azure 的支持，可以[创建和消费云资源](../../end-user/components/cloud-services/provision-and-consume-cloud-services)：
|
||||
|
||||
参考 [Authenticate Terraform to Azure](https://docs.microsoft.com/en-us/azure/developer/terraform/authenticate-to-azure?tabs=bash)，设置如下参数。
|
||||
|
||||
|
|
@ -30,7 +30,7 @@ title: 云资源插件
|
|||
|
||||
## AWS Terraform Provider 插件
|
||||
|
||||
执行如下命令开启 Terraform 对 AWS 的支持，可以[创建和消费云资源](../../end-user/components/cloud-services/provider-and-consume-cloud-services)：
|
||||
执行如下命令开启 Terraform 对 AWS 的支持，可以[创建和消费云资源](../../end-user/components/cloud-services/provision-and-consume-cloud-services)：
|
||||
|
||||
参考 [Authenticate Terraform to AWS](https://registry.terraform.io/providers/hashicorp/aws/latest/docs#environment-variables)，设置如下参数。
|
||||
|
||||
|
|
|
|||
Binary file not shown.
|
After Width: | Height: | Size: 270 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 46 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 29 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 9.2 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 40 KiB |
|
|
@ -5,11 +5,11 @@ description: 本文介绍通过 KubeVela 交付云厂商提供的服务，并能
|
|||
|
||||
集成云服务是实际开发中最频繁的使用需求之一。从基础的对象存储、云数据库到负载均衡、云缓存，再到基于业务的搜索引擎等等，快速的接入云服务并便捷的使用它们可以大大降低开发成本。与此同时，由于可供选择的云服务厂商非常多，多云交付已成为未来必然形态，如何管理好接入混合云环境时各类资源之间的关系，也成为必须解决的最大挑战。
|
||||
|
||||
在本文中，我们以交付阿里云 RDS 服务为例，为大家介绍 KubeVela 交付云服务的使用方式。
|
||||
在本文中，我们介绍一个例子，向你展示如何部署云服务。
|
||||
|
||||
## 开始之前
|
||||
|
||||
- 开通云厂商账户，根据权限最小化原则，分配好可获取 AK/SK 的子账号。阿里云请参考 [创建 RAM 用户](https://help.aliyun.com/document_detail/121941.html)。
|
||||
- 拥有一个能适当权限访问你的目标云资源的云供应商账户
|
||||
|
||||
- 确保云账号具有足够的费用。
|
||||
|
||||
|
|
@ -17,75 +17,107 @@ description: 本文介绍通过 KubeVela 交付云厂商提供的服务，并能
|
|||
|
||||
## 开启对应云服务商的插件
|
||||
|
||||
首先我们打开 VelaUX Dashboard，选择左侧第四个选项卡 `Addon` ，点开 terraform-alibaba：
|
||||
首先，访问[VelaUX (KubeVela Dashboard)](../install#3-安装-VelaUX)，切换到 "Addon" 标签，并点击 addon
|
||||
`terraform-xxx`。`xxx`代表云提供商的名称。我们支持以下的插件：
|
||||
|
||||
接着填入你的 ALICLOUD_ACCESS_KEY，ALICLOUD_REGION 和 ALICLOUD_SECRET_KEY 来 Enable 它。
|
||||
- provider-alibaba
|
||||
- provider-aws
|
||||
- provider-azure
|
||||
- provider-tencent
|
||||
|
||||
> 注意：KubeVela 会加密存储以上所有的密钥信息，不用担心泄漏风险
|
||||
我们可以分别在阿里巴巴云、AWS、Azure 和腾讯云配置云资源。
|
||||
|
||||
按照每个云提供商的插件的所有属性上的说明来设置插件并启用它。
|
||||
|
||||
例如，对于阿里巴巴云，你需要设置以下属性：
|
||||
> 注意。KubeVela对所有的密钥进行了加密，因此不必担心它的安全问题。
|
||||
|
||||
|
||||
|
||||
`terraform-alibaba` 插件依赖 `terraform` 插件，如果后者未启用，它会自动被启用。云资源的创建过程需要从 Github 中获取云服务配置文件，如果你的管控集群所在网络访问 Github 受限，你可以打开 `terraform` 插件管理页面开启 `GithubBlocked` 选项。
|
||||
然后填写你的ALICLOUD_ACCESS_KEY，ALICLOUD_REGION，和ALICLOUD_SECRET_KEY来启用它。
|
||||
|
||||
`terraform-alibaba` 插件提供了以下类型资源的支持，并持续增加中：
|
||||
云服务的创建过程会从GitHub中提取配置。如果你的控制平面 运行KubeVela的集群很难连接到GitHub，请在`terraform`插件中打开`GithubBlocked`选项。
|
||||
|
||||
- alibaba-rds
|
||||
- alibaba-ack
|
||||
- alibaba-ask
|
||||
- alibaba-oss
|
||||
- alibaba-rds
|
||||
- alibaba-redis
|
||||
KubeVela支持以下类型的资源，以后还会有更多：
|
||||
|
||||
## 设置交付目标参数
|
||||
| 编排类型 | 云服务商 | 云资源 | 描述 |
|
||||
|-----------|-------|------------------------------------------------------------------------------------------|-----------------------------------------------------------------------|
|
||||
| Terraform | 阿里云 | [ACK](../end-user/components/cloud-services/terraform/alibaba-ack) | Terraform configuration for Alibaba Cloud ACK cluster |
|
||||
| | | [ASK](../end-user/components/cloud-services/terraform/alibaba-ask) | Terraform configuration for Alibaba Cloud Serverless Kubernetes (ASK) |
|
||||
| | | [EIP](../end-user/components/cloud-services/terraform/alibaba-eip) | Terraform configuration for Alibaba Cloud EIP |
|
||||
| | | [OSS](../end-user/components/cloud-services/terraform/alibaba-oss) | Terraform configuration for Alibaba Cloud OSS |
|
||||
| | | [RDS](../end-user/components/cloud-services/terraform/alibaba-rds) | Terraform configuration for Alibaba Cloud RDS |
|
||||
| | | [Redis](../end-user/components/cloud-services/terraform/alibaba-redis) | Terraform configuration for Alibaba Cloud Redis |
|
||||
| | | [SLS Project](../end-user/components/cloud-services/terraform/alibaba-sls-project) | Terraform configuration for Alibaba Cloud SLS Project |
|
||||
| | | [SLS Store](../end-user/components/cloud-services/terraform/alibaba-sls-store) | Terraform configuration for Alibaba Cloud SLS Store |
|
||||
| | | [VPC](../end-user/components/cloud-services/terraform/alibaba-vpc) | Terraform configuration for Alibaba Cloud VPC |
|
||||
| | | [VSwitch](../end-user/components/cloud-services/terraform/alibaba-vswitch) | Terraform configuration for Alibaba Cloud VSwitch |
|
||||
| | AWS | [S3](../end-user/components/cloud-services/terraform/aws-s3) | Terraform configuration for AWS S3 bucket |
|
||||
| | Azure | [Mariadb](../end-user/components/cloud-services/terraform/azure-database-mariadb) | Terraform configuration for Azure Database Mariadb |
|
||||
| | | [Storage Account](../end-user/components/cloud-services/terraform/azure-storage-account) | Terraform configuration for Azure Storage Account |
|
||||
|
||||
云资源的交付模型与其他应用不同，它的控制器只会在管控集群运行，创建多云/多可用区的云服务。因此，我们需要在交付目标中设置每一个目标所处的云厂商和区域参数。
|
||||
进入交付目标管理页面，选择你需要使用云资源的目标区域，点击 `Edit` 进入编辑窗口，或直接创建新的交付目标。
|
||||
|
||||
|
||||
## 创建你的云服务
|
||||
|
||||
交付目标首先主要描述的是 Kubernetes 集群的 Namespace，然后通过设置共享变量的方式描述该集群所处的云厂商和区域。
|
||||
首先[创建一个应用程序](../how-to/dashboard/application/create-application)。请选择你的云服务的类型。
|
||||
其前缀为`aws-`、`azure`、`alibaba-`或 `tencent-`。
|
||||
|
||||
- Cloud Service Provider: 云服务提供商，与 AK/SK 绑定，`terraform-alibaba` 默认生成的名称是 `default`，因此这里填入 default 即可。
|
||||
- Region: 地域，创建云服务时基于此参数选择地域。你应该填写当前交付目标所描述的 Kubernetes 集群所在地域，以便 Kubernetes 中的应用可直接访问交付的云服务。
|
||||
对于不同的供应商，这些参数会相应更新。
|
||||
|
||||
## 创建你需要的云资源应用
|
||||
例如，`aws-s3` 有以下参数。
|
||||
|
||||
设置完交付目标后，让我们点击左侧第一个 `Applications` 选项卡进入应用管理页面，点击右上角的 `New Application` 开始创建应用。与其他类型的应用一样，你仅需要选择你想要部署的云服务类型，比如我们选择 `alibaba-rds`，选择环境，请注意，选择的环境包括的交付目标必须都设置了 `Cloud Service Provider` 和 `Region` 参数。
|
||||
|
||||
|
||||
点击 `Next Step` 按钮进入部署参数设置页面，对于不同的云服务有不同的设置参数，以 `alibaba-rds` 为例，支持以下参数：
|
||||
`azure-database-mariadb` 有以下参数。
|
||||
|
||||
- InstanceName: 实例名称
|
||||
- DatabaseName: 数据库名称
|
||||
- AccountName: 默认生成的账号名称
|
||||
- Password: 默认生成的账号密码
|
||||
- AllocatePublicConnection: 是否分配公网访问地址
|
||||
- DeleteResource: 是否在应用删除时删除对应的云服务
|
||||
- Privilege: 默认生成的账号权限
|
||||
|
||||
|
||||
|
||||
`alibaba-rds` 有以下参数。
|
||||
|
||||
对于其他云资源，可直接阅读每个字段的说明即可。按照你的需求设置以上参数，点击 `Create` 进入应用管理页面后，点击部署按钮即可开始云服务的部署。
|
||||
|
||||
|
||||
## 查看云资源创建状态
|
||||
所有的云资源都有一些共同的参数。
|
||||
|
||||
与普通应用一样，云服务应用也是需要切换到对应环境页面下查看实例信息。默认情况下一个环境下有几个交付目标，云服务即会生成对应数量的实例。
|
||||
- DeleteResource：当应用程序被删除时，是否要删除相应的云服务
|
||||
- ProviderRef：被云服务引用的提供者。
|
||||
- Region：Region是云提供商的区域。它将覆盖`providerRef`。
|
||||
|
||||
|
||||
根据你的需要设置上述参数，完成应用程序的创建，然后[部署应用程序](../how-to/dashboard/application/deploy-application)。
|
||||
|
||||
在实例列表中，展示实例名称、状态、资源类型和所在地域。初始情况下，名字为空，因为云服务实例的生成需要一定时间，当实例正常生成后名称即可出现。点击名称即可进入资源对应的云厂商控制台页面。
|
||||
##查看云资源创建状态
|
||||
|
||||
- 查看云实例列表
|
||||
|
||||
与其他应用程序一样，云服务应用程序也需要切换到相应的环境页面来查看实例信息。 默认情况下，一个环境中有多个目标，云服务会生成相应数量的实例。
|
||||
|
||||
|
||||
|
||||
在实例列表中，会显示实例名称、状态、资源类型和位置。在开始时，名称是空的。 因为云服务实例的生成需要一定的时间，当实例正常生成后，名称会出现。
|
||||
|
||||
- 在云提供商的控制台中查看云资源
|
||||
|
||||
您可以在云提供商的控制台中访问该实例。例如，您可以检查名称或控制台来访问它。
|
||||
|
||||
|
||||
例如，你可以在[https://console.aliyun.com](https://console.aliyun.com)中查看阿里巴巴云RDS实例。
|
||||
|
||||
|
||||
|
||||
- 检查云实例的细节和状态
|
||||
|
||||
点击 "检查细节 "按钮来查看应用程序的细节。
|
||||
|
||||
|
||||
|
||||
点击 `Check the detail` 按钮，查看应用详情，你会发现每一个实例对应生成了 Secret 资源，该资源一般记录的该服务的访问地址和密钥等信息。Secret 资源会在管控集群存在同时分发到交付目标所处的集群和 Namespace。因此处在同一个环境下的其他应用可以直接在环境变量中直接应用该资源获取通信地址和密钥。
|
||||
你会发现，每个实例都会生成一个Secret资源，一般来说，它记录了服务的访问地址和密钥信息。秘密资源将被分配到目标所在的集群和命名空间，而
|
||||
控制集群存在。因此，同一环境中的其他应用程序可以直接使用资源中的环境变量来获取访问地址和密钥。
|
||||
|
||||
|
||||
|
||||
在最后一节 `Component Status` 中，显示了云服务实例的健康状态和信息。
|
||||
|
||||
## 常见错误
|
||||
|
||||
- 云服务实例处在 ProviderNotReady 状态
|
||||
|
||||
> 首先需要确定是否按照文档指引正确设置了交付目标的参数。然后确定 AK/SK 是正确且对应用户具有创建该资源的权限。
|
||||
|
||||
- 云服务一直处在 ProvisioningAndChecking 状态，且无名称。
|
||||
|
||||
> 云服务的创建一般需要一定时间，请等候或者进入云厂商控制台查看创建进度。
|
||||
|
|
@ -8,8 +8,7 @@ title: 创建和使用云资源
|
|||
KubeVela 通过云资源组件（Component）和运维特征（Trait）里的资源绑定功能，高效安全地完成不同类型云资源的集成工作。目前你可以直接调用下面这些云资源默认组件。
|
||||
同时在未来，更多新的云资源也会在社区的支撑下逐渐成为默认选项，让你标准化统一地去使用各种厂商的云资源。
|
||||
|
||||
> ⚠️ 请确认管理员已经安装了 [Terraform 插件 'terraform/provider-alicloud'](../../../install#4-【可选】安装插件).
|
||||
|
||||
> ⚠️ 请确认管理员已经安装了 [云资源插件](../../../reference/addons/terraform)。
|
||||
|
||||
## 支持的云资源列表
|
||||
|
||||
|
|
@ -6,7 +6,7 @@ title: 扩展云资源
|
|||
Terraform 是目前业内支持云资源最广泛也最受欢迎的组件，KubeVela 对 Terraform 进行了额外的支持，使得用户可以通过 Kubernetes CRD 的方式配合
|
||||
Terraform 使用任意的云资源。
|
||||
|
||||
为了使最终用户能够[部署和消费云资源](../../end-user/components/cloud-services/provider-and-consume-cloud-services)，当用户的要求超出了 [内置云资源的能力](../../end-user/components/cloud-services/provider-and-consume-cloud-services)，
|
||||
为了使最终用户能够[部署和消费云资源](../../end-user/components/cloud-services/provision-and-consume-cloud-services)，当用户的要求超出了 [内置云资源的能力](../../end-user/components/cloud-services/provision-and-consume-cloud-services)，
|
||||
管理员需要要为云资源准备 ComponentDefinitions。
|
||||
|
||||
以下是为云供应商阿里云、AWS 和 Azure 创建 Terraform 类型的云资源 ComponentDefinitions 的指南。
|
||||
|
|
@ -159,7 +159,7 @@ $ vela show alibaba-eip
|
|||
+-----------+-----------------------------------------------------------------------------+--------+----------+---------+
|
||||
```
|
||||
|
||||
如果表格能正常出来，ComponentDefinition 应该就可以工作了。更进一步，你可以通过文档[部署云资源](../../end-user/components/cloud-services/provider-and-consume-cloud-services)创建一个实际的 EIP 来验证。
|
||||
如果表格能正常出来，ComponentDefinition 应该就可以工作了。更进一步，你可以通过文档[部署云资源](../../end-user/components/cloud-services/provision-and-consume-cloud-services)创建一个实际的 EIP 来验证。
|
||||
|
||||
## 生成文档
|
||||
|
||||
|
|
|
|||
|
|
@ -9,10 +9,10 @@ title: 云资源插件
|
|||
|
||||
## 阿里云 Terraform Provider 插件
|
||||
|
||||
执行如下命令开启 Terraform 对阿里云的支持，可以[创建和消费云资源](../../end-user/components/cloud-services/provider-and-consume-cloud-services)：
|
||||
执行如下命令开启 Terraform 对阿里云的支持，可以[创建和消费云资源](../../end-user/components/cloud-services/provision-and-consume-cloud-services)：
|
||||
|
||||
其中，请参考[如何获取 Access Key](https://help.aliyun.com/knowledge_detail/38738.html)设置 Access Key，参考 [Region 列表](https://www.alibabacloud.com/help/doc-detail/72379.htm) 中的 `RegionId` 设置 `ALICLOUD_REGION`。
|
||||
参数 `ALICLOUD_SECURITY_TOKEN` 是可选的，你可以通过 [这篇介绍](https://www.alibabacloud.com/help/zh/doc-detail/28756.htm) 设置。
|
||||
其中，请参考[如何获取 Access Key](https://help.aliyun.com/knowledge_detail/38738.html)设置 Access Key，参考 [Region 列表](https://www.alibabacloud.com/help/doc-detail/72379.htm) 中的 `RegionId` 设置 `ALICLOUD_REGION`。
|
||||
参数 `ALICLOUD_SECURITY_TOKEN` 是可选的，你可以通过 [这篇介绍](https://www.alibabacloud.com/help/zh/doc-detail/28756.htm) 设置。
|
||||
|
||||
```shell
|
||||
vela addon enable provider-alibaba ALICLOUD_ACCESS_KEY=<xxx> ALICLOUD_SECRET_KEY=<yyy> ALICLOUD_REGION=<region>
|
||||
|
|
@ -20,9 +20,9 @@ title: 云资源插件
|
|||
|
||||
## Azure Terraform Provider 插件
|
||||
|
||||
执行如下命令开启 Terraform 对 Azure 的支持，可以[创建和消费云资源](../../end-user/components/cloud-services/provider-and-consume-cloud-services)：
|
||||
执行如下命令开启 Terraform 对 Azure 的支持，可以[创建和消费云资源](../../end-user/components/cloud-services/provision-and-consume-cloud-services)：
|
||||
|
||||
参考 [Authenticate Terraform to Azure](https://docs.microsoft.com/en-us/azure/developer/terraform/authenticate-to-azure?tabs=bash)，设置如下参数。
|
||||
参考 [Authenticate Terraform to Azure](https://docs.microsoft.com/en-us/azure/developer/terraform/authenticate-to-azure?tabs=bash)，设置如下参数。
|
||||
|
||||
```shell
|
||||
vela addon enable provider-azure ARM_CLIENT_ID=<aaa> ARM_CLIENT_SECRET=<bbb> ARM_SUBSCRIPTION_ID=<ccc> ARM_TENANT_ID=<ddd>
|
||||
|
|
@ -30,9 +30,9 @@ title: 云资源插件
|
|||
|
||||
## AWS Terraform Provider 插件
|
||||
|
||||
执行如下命令开启 Terraform 对 AWS 的支持，可以[创建和消费云资源](../../end-user/components/cloud-services/provider-and-consume-cloud-services)：
|
||||
执行如下命令开启 Terraform 对 AWS 的支持，可以[创建和消费云资源](../../end-user/components/cloud-services/provision-and-consume-cloud-services)：
|
||||
|
||||
参考 [Authenticate Terraform to AWS](https://registry.terraform.io/providers/hashicorp/aws/latest/docs#environment-variables)，设置如下参数。
|
||||
参考 [Authenticate Terraform to AWS](https://registry.terraform.io/providers/hashicorp/aws/latest/docs#environment-variables)，设置如下参数。
|
||||
|
||||
```shell
|
||||
vela addon enable provider-aws AWS_ACCESS_KEY_ID=<aaa> AWS_SECRET_ACCESS_KEY=<bbb> AWS_DEFAULT_REGION=<region>
|
||||
|
|
|
|||
Binary file not shown.
|
After Width: | Height: | Size: 270 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 46 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 29 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 9.2 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 40 KiB |
|
|
@ -5,11 +5,11 @@ description: 本文介绍通过 KubeVela 交付云厂商提供的服务，并能
|
|||
|
||||
集成云服务是实际开发中最频繁的使用需求之一。从基础的对象存储、云数据库到负载均衡、云缓存，再到基于业务的搜索引擎等等，快速的接入云服务并便捷的使用它们可以大大降低开发成本。与此同时，由于可供选择的云服务厂商非常多，多云交付已成为未来必然形态，如何管理好接入混合云环境时各类资源之间的关系，也成为必须解决的最大挑战。
|
||||
|
||||
在本文中，我们以交付阿里云 RDS 服务为例，为大家介绍 KubeVela 交付云服务的使用方式。
|
||||
在本文中，我们介绍一个例子，向你展示如何部署云服务。
|
||||
|
||||
## 开始之前
|
||||
|
||||
- 开通云厂商账户，根据权限最小化原则，分配好可获取 AK/SK 的子账号。阿里云请参考 [创建 RAM 用户](https://help.aliyun.com/document_detail/121941.html)。
|
||||
- 拥有一个能适当权限访问你的目标云资源的云供应商账户
|
||||
|
||||
- 确保云账号具有足够的费用。
|
||||
|
||||
|
|
@ -17,75 +17,107 @@ description: 本文介绍通过 KubeVela 交付云厂商提供的服务，并能
|
|||
|
||||
## 开启对应云服务商的插件
|
||||
|
||||
首先我们打开 VelaUX Dashboard，选择左侧第四个选项卡 `Addon` ，点开 terraform-alibaba：
|
||||
首先，访问[VelaUX (KubeVela Dashboard)](../install#3-安装-VelaUX)，切换到 "Addon" 标签，并点击 addon
|
||||
`terraform-xxx`。`xxx`代表云提供商的名称。我们支持以下的插件：
|
||||
|
||||
接着填入你的 ALICLOUD_ACCESS_KEY，ALICLOUD_REGION 和 ALICLOUD_SECRET_KEY 来 Enable 它。
|
||||
- provider-alibaba
|
||||
- provider-aws
|
||||
- provider-azure
|
||||
- provider-tencent
|
||||
|
||||
> 注意：KubeVela 会加密存储以上所有的密钥信息，不用担心泄漏风险
|
||||
我们可以分别在阿里巴巴云、AWS、Azure 和腾讯云配置云资源。
|
||||
|
||||
按照每个云提供商的插件的所有属性上的说明来设置插件并启用它。
|
||||
|
||||
例如，对于阿里巴巴云，你需要设置以下属性：
|
||||
> 注意。KubeVela对所有的密钥进行了加密，因此不必担心它的安全问题。
|
||||
|
||||
|
||||
|
||||
`terraform-alibaba` 插件依赖 `terraform` 插件，如果后者未启用，它会自动被启用。云资源的创建过程需要从 Github 中获取云服务配置文件，如果你的管控集群所在网络访问 Github 受限，你可以打开 `terraform` 插件管理页面开启 `GithubBlocked` 选项。
|
||||
然后填写你的ALICLOUD_ACCESS_KEY，ALICLOUD_REGION，和ALICLOUD_SECRET_KEY来启用它。
|
||||
|
||||
`terraform-alibaba` 插件提供了以下类型资源的支持，并持续增加中：
|
||||
云服务的创建过程会从GitHub中提取配置。如果你的控制平面 运行KubeVela的集群很难连接到GitHub，请在`terraform`插件中打开`GithubBlocked`选项。
|
||||
|
||||
- alibaba-rds
|
||||
- alibaba-ack
|
||||
- alibaba-ask
|
||||
- alibaba-oss
|
||||
- alibaba-rds
|
||||
- alibaba-redis
|
||||
KubeVela支持以下类型的资源，以后还会有更多：
|
||||
|
||||
## 设置交付目标参数
|
||||
| 编排类型 | 云服务商 | 云资源 | 描述 |
|
||||
|-----------|-------|------------------------------------------------------------------------------------------|-----------------------------------------------------------------------|
|
||||
| Terraform | 阿里云 | [ACK](../end-user/components/cloud-services/terraform/alibaba-ack) | Terraform configuration for Alibaba Cloud ACK cluster |
|
||||
| | | [ASK](../end-user/components/cloud-services/terraform/alibaba-ask) | Terraform configuration for Alibaba Cloud Serverless Kubernetes (ASK) |
|
||||
| | | [EIP](../end-user/components/cloud-services/terraform/alibaba-eip) | Terraform configuration for Alibaba Cloud EIP |
|
||||
| | | [OSS](../end-user/components/cloud-services/terraform/alibaba-oss) | Terraform configuration for Alibaba Cloud OSS |
|
||||
| | | [RDS](../end-user/components/cloud-services/terraform/alibaba-rds) | Terraform configuration for Alibaba Cloud RDS |
|
||||
| | | [Redis](../end-user/components/cloud-services/terraform/alibaba-redis) | Terraform configuration for Alibaba Cloud Redis |
|
||||
| | | [SLS Project](../end-user/components/cloud-services/terraform/alibaba-sls-project) | Terraform configuration for Alibaba Cloud SLS Project |
|
||||
| | | [SLS Store](../end-user/components/cloud-services/terraform/alibaba-sls-store) | Terraform configuration for Alibaba Cloud SLS Store |
|
||||
| | | [VPC](../end-user/components/cloud-services/terraform/alibaba-vpc) | Terraform configuration for Alibaba Cloud VPC |
|
||||
| | | [VSwitch](../end-user/components/cloud-services/terraform/alibaba-vswitch) | Terraform configuration for Alibaba Cloud VSwitch |
|
||||
| | AWS | [S3](../end-user/components/cloud-services/terraform/aws-s3) | Terraform configuration for AWS S3 bucket |
|
||||
| | Azure | [Mariadb](../end-user/components/cloud-services/terraform/azure-database-mariadb) | Terraform configuration for Azure Database Mariadb |
|
||||
| | | [Storage Account](../end-user/components/cloud-services/terraform/azure-storage-account) | Terraform configuration for Azure Storage Account |
|
||||
|
||||
云资源的交付模型与其他应用不同，它的控制器只会在管控集群运行，创建多云/多可用区的云服务。因此，我们需要在交付目标中设置每一个目标所处的云厂商和区域参数。
|
||||
进入交付目标管理页面，选择你需要使用云资源的目标区域，点击 `Edit` 进入编辑窗口，或直接创建新的交付目标。
|
||||
|
||||
|
||||
## 创建你的云服务
|
||||
|
||||
交付目标首先主要描述的是 Kubernetes 集群的 Namespace，然后通过设置共享变量的方式描述该集群所处的云厂商和区域。
|
||||
首先[创建一个应用程序](../how-to/dashboard/application/create-application)。请选择你的云服务的类型。
|
||||
其前缀为`aws-`、`azure`、`alibaba-`或 `tencent-`。
|
||||
|
||||
- Cloud Service Provider: 云服务提供商，与 AK/SK 绑定，`terraform-alibaba` 默认生成的名称是 `default`，因此这里填入 default 即可。
|
||||
- Region: 地域，创建云服务时基于此参数选择地域。你应该填写当前交付目标所描述的 Kubernetes 集群所在地域，以便 Kubernetes 中的应用可直接访问交付的云服务。
|
||||
对于不同的供应商，这些参数会相应更新。
|
||||
|
||||
## 创建你需要的云资源应用
|
||||
例如，`aws-s3` 有以下参数。
|
||||
|
||||
设置完交付目标后，让我们点击左侧第一个 `Applications` 选项卡进入应用管理页面，点击右上角的 `New Application` 开始创建应用。与其他类型的应用一样，你仅需要选择你想要部署的云服务类型，比如我们选择 `alibaba-rds`，选择环境，请注意，选择的环境包括的交付目标必须都设置了 `Cloud Service Provider` 和 `Region` 参数。
|
||||
|
||||
|
||||
点击 `Next Step` 按钮进入部署参数设置页面，对于不同的云服务有不同的设置参数，以 `alibaba-rds` 为例，支持以下参数：
|
||||
`azure-database-mariadb` 有以下参数。
|
||||
|
||||
- InstanceName: 实例名称
|
||||
- DatabaseName: 数据库名称
|
||||
- AccountName: 默认生成的账号名称
|
||||
- Password: 默认生成的账号密码
|
||||
- AllocatePublicConnection: 是否分配公网访问地址
|
||||
- DeleteResource: 是否在应用删除时删除对应的云服务
|
||||
- Privilege: 默认生成的账号权限
|
||||
|
||||
|
||||
|
||||
`alibaba-rds` 有以下参数。
|
||||
|
||||
对于其他云资源，可直接阅读每个字段的说明即可。按照你的需求设置以上参数，点击 `Create` 进入应用管理页面后，点击部署按钮即可开始云服务的部署。
|
||||
|
||||
|
||||
## 查看云资源创建状态
|
||||
所有的云资源都有一些共同的参数。
|
||||
|
||||
与普通应用一样，云服务应用也是需要切换到对应环境页面下查看实例信息。默认情况下一个环境下有几个交付目标，云服务即会生成对应数量的实例。
|
||||
- DeleteResource：当应用程序被删除时，是否要删除相应的云服务
|
||||
- ProviderRef：被云服务引用的提供者。
|
||||
- Region：Region是云提供商的区域。它将覆盖`providerRef`。
|
||||
|
||||
|
||||
根据你的需要设置上述参数，完成应用程序的创建，然后[部署应用程序](../how-to/dashboard/application/deploy-application)。
|
||||
|
||||
在实例列表中，展示实例名称、状态、资源类型和所在地域。初始情况下，名字为空，因为云服务实例的生成需要一定时间，当实例正常生成后名称即可出现。点击名称即可进入资源对应的云厂商控制台页面。
|
||||
##查看云资源创建状态
|
||||
|
||||
- 查看云实例列表
|
||||
|
||||
与其他应用程序一样，云服务应用程序也需要切换到相应的环境页面来查看实例信息。 默认情况下，一个环境中有多个目标，云服务会生成相应数量的实例。
|
||||
|
||||
|
||||
|
||||
在实例列表中，会显示实例名称、状态、资源类型和位置。在开始时，名称是空的。 因为云服务实例的生成需要一定的时间，当实例正常生成后，名称会出现。
|
||||
|
||||
- 在云提供商的控制台中查看云资源
|
||||
|
||||
您可以在云提供商的控制台中访问该实例。例如，您可以检查名称或控制台来访问它。
|
||||
|
||||
|
||||
例如，你可以在[https://console.aliyun.com](https://console.aliyun.com)中查看阿里巴巴云RDS实例。
|
||||
|
||||
|
||||
|
||||
- 检查云实例的细节和状态
|
||||
|
||||
点击 "检查细节 "按钮来查看应用程序的细节。
|
||||
|
||||
|
||||
|
||||
点击 `Check the detail` 按钮，查看应用详情，你会发现每一个实例对应生成了 Secret 资源，该资源一般记录的该服务的访问地址和密钥等信息。Secret 资源会在管控集群存在同时分发到交付目标所处的集群和 Namespace。因此处在同一个环境下的其他应用可以直接在环境变量中直接应用该资源获取通信地址和密钥。
|
||||
你会发现，每个实例都会生成一个Secret资源，一般来说，它记录了服务的访问地址和密钥信息。秘密资源将被分配到目标所在的集群和命名空间，而
|
||||
控制集群存在。因此，同一环境中的其他应用程序可以直接使用资源中的环境变量来获取访问地址和密钥。
|
||||
|
||||
|
||||
|
||||
在最后一节 `Component Status` 中，显示了云服务实例的健康状态和信息。
|
||||
|
||||
## 常见错误
|
||||
|
||||
- 云服务实例处在 ProviderNotReady 状态
|
||||
|
||||
> 首先需要确定是否按照文档指引正确设置了交付目标的参数。然后确定 AK/SK 是正确且对应用户具有创建该资源的权限。
|
||||
|
||||
- 云服务一直处在 ProvisioningAndChecking 状态，且无名称。
|
||||
|
||||
> 云服务的创建一般需要一定时间，请等候或者进入云厂商控制台查看创建进度。
|
||||
|
|
@ -93,7 +93,7 @@ module.exports = {
|
|||
items: [
|
||||
"end-user/quick-start-cli",
|
||||
"end-user/traits/ingress",
|
||||
"end-user/components/cloud-services/provider-and-consume-cloud-services",
|
||||
"end-user/components/cloud-services/provision-and-consume-cloud-services",
|
||||
"end-user/traits/rollout",
|
||||
"end-user/policies/health",
|
||||
"case-studies/multi-cluster",
|
||||
|
|
|
|||
|
|
@ -13,7 +13,7 @@ You can use cloud resources of various manufacturers in a standardized and unifi
|
|||
|
||||
This tutorial will talk about how to provision and consume Cloud Resources by Terraform.
|
||||
|
||||
> ⚠️ This section requires your platform engineers have already enabled [add-on 'terraform/provider-alicloud'](../../../install#4-optional-enable-addons).
|
||||
> ⚠️ This section requires your platform engineers have already enabled [cloud resources addon](../../../reference/addons/terraform).
|
||||
|
||||
## Supported Cloud Resource list
|
||||
|
||||
|
|
@ -2,9 +2,9 @@
|
|||
title: Extend Cloud Resources
|
||||
---
|
||||
|
||||
To enable end users to [provision and consume cloud resources](../../end-user/components/cloud-services/provider-and-consume-cloud-services),
|
||||
To enable end users to [provision and consume cloud resources](../../end-user/components/cloud-services/provision-and-consume-cloud-services),
|
||||
platform engineers need to prepare ComponentDefinitions for cloud resources if end users' requirements are beyond the
|
||||
[built-in capabilities](../../end-user/components/cloud-services/provider-and-consume-cloud-services#supported-cloud-resource-list).
|
||||
[built-in capabilities](../../end-user/components/cloud-services/provision-and-consume-cloud-services#supported-cloud-resource-list).
|
||||
|
||||
Here is the guide to create Terraform typed ComponentDefinitions of cloud resources for cloud providers Alibaba Cloud, AWS and Azure.
|
||||
|
||||
|
|
@ -157,7 +157,7 @@ $ vela show alibaba-eip
|
|||
```
|
||||
|
||||
If the tables display, the ComponentDefinition should work. To take a step further, you can verify it by provision an actual EIP instance per
|
||||
the doc [Provision cloud resources](../../end-user/components/cloud-services/provider-and-consume-cloud-services#provision-cloud-resources).
|
||||
the doc [Provision cloud resources](../../end-user/components/cloud-services/provision-and-consume-cloud-services#provision-cloud-resources).
|
||||
|
||||
## Generate documentation
|
||||
|
||||
|
|
|
|||
|
|
@ -11,10 +11,10 @@ title: Addon Cloud Resources
|
|||
|
||||
## Terraform Provider addon for Alibaba Cloud
|
||||
|
||||
Enable Terraform Alibaba Cloud Provider as below to [provision and/or consume cloud resources](../../end-user/components/cloud-services/provider-and-consume-cloud-services).
|
||||
Enable Terraform Alibaba Cloud Provider as below to [provision and/or consume cloud resources](../../end-user/components/cloud-services/provision-and-consume-cloud-services).
|
||||
|
||||
Here is how to get [access key](https://help.aliyun.com/knowledge_detail/38738.html). Set the value for `ALICLOUD_REGION` by picking one `RegionId` from [Alibaba Cloud region list](https://www.alibabacloud.com/help/doc-detail/72379.htm).
|
||||
You can also set the value for parameter `ALICLOUD_SECURITY_TOKEN`, which is optional, per [this doc](https://www.alibabacloud.com/help/doc-detail/28756.htm).
|
||||
Here is how to get [access key](https://help.aliyun.com/knowledge_detail/38738.html). Set the value for `ALICLOUD_REGION` by picking one `RegionId` from [Alibaba Cloud region list](https://www.alibabacloud.com/help/doc-detail/72379.htm).
|
||||
You can also set the value for parameter `ALICLOUD_SECURITY_TOKEN`, which is optional, per [this doc](https://www.alibabacloud.com/help/doc-detail/28756.htm).
|
||||
|
||||
```shell
|
||||
vela addon enable provider-alibaba ALICLOUD_ACCESS_KEY=<xxx> ALICLOUD_SECRET_KEY=<yyy> ALICLOUD_REGION=<region>
|
||||
|
|
@ -22,9 +22,9 @@ title: Addon Cloud Resources
|
|||
|
||||
## Terraform Provider addon for Azure
|
||||
|
||||
Enable Terraform Azure Provider as below to [provision and/or consume cloud resources](../../end-user/components/cloud-services/provider-and-consume-cloud-services).
|
||||
Enable Terraform Azure Provider as below to [provision and/or consume cloud resources](../../end-user/components/cloud-services/provision-and-consume-cloud-services).
|
||||
|
||||
Set these parameters below per [Authenticate Terraform to Azure](https://docs.microsoft.com/en-us/azure/developer/terraform/authenticate-to-azure?tabs=bash).
|
||||
Set these parameters below per [Authenticate Terraform to Azure](https://docs.microsoft.com/en-us/azure/developer/terraform/authenticate-to-azure?tabs=bash).
|
||||
|
||||
```shell
|
||||
vela addon enable provider-azure ARM_CLIENT_ID=<aaa> ARM_CLIENT_SECRET=<bbb> ARM_SUBSCRIPTION_ID=<ccc> ARM_TENANT_ID=<ddd>
|
||||
|
|
@ -32,9 +32,9 @@ title: Addon Cloud Resources
|
|||
|
||||
## Terraform Provider addon for AWS
|
||||
|
||||
Enable Terraform AWS Provider as below to [provision and/or consume cloud resources](../../end-user/components/cloud-services/provider-and-consume-cloud-services).
|
||||
Enable Terraform AWS Provider as below to [provision and/or consume cloud resources](../../end-user/components/cloud-services/provision-and-consume-cloud-services).
|
||||
|
||||
Set these parameters below per [Authenticate Terraform to AWS](https://registry.terraform.io/providers/hashicorp/aws/latest/docs#environment-variables).
|
||||
Set these parameters below per [Authenticate Terraform to AWS](https://registry.terraform.io/providers/hashicorp/aws/latest/docs#environment-variables).
|
||||
|
||||
```shell
|
||||
vela addon enable provider-aws AWS_ACCESS_KEY_ID=<aaa> AWS_SECRET_ACCESS_KEY=<bbb> AWS_DEFAULT_REGION=<region>
|
||||
|
|
|
|||
|
|
@ -25,40 +25,46 @@ First, visit [VelaUX (KubeVela Dashboard)](../install#3-install-velaux), switch
|
|||
- provider-alibaba
|
||||
- provider-aws
|
||||
- provider-azure
|
||||
- provider-tencent
|
||||
|
||||
We can provision cloud resources in Alibaba Cloud, AWS, and Azure respectively.
|
||||
We can provision cloud resources in Alibaba Cloud, AWS, Azure and Tencent Cloud respectively.
|
||||
|
||||
Follow the instructions on all the properties of the addon for each cloud provider to set the addon and enable it.
|
||||
|
||||
For example, for Alibaba Cloud, you need to set the following properties:
|
||||
Then fill in your ALICLOUD_ACCESS_KEY, ALICLOUD_REGION, and ALICLOUD_SECRET_KEY to enable it。
|
||||
|
||||
> Notice: KubeVela encrypts all the keys, hence no need to worry about its safety.
|
||||
|
||||
|
||||
|
||||
Then fill in your ALICLOUD_ACCESS_KEY, ALICLOUD_REGION, and ALICLOUD_SECRET_KEY to enable it。
|
||||
|
||||
The creating process of cloud services pulls configuration from GitHub. If your control plane
|
||||
cluster that runs KubeVela is very hard to connect to GitHub, please open up the `GithubBlocked` option in `terraform`
|
||||
addon.
|
||||
|
||||
KubeVela supports the following types of resources and more later on:
|
||||
|
||||
Cloud Provider | Cloud Resource | Description
|
||||
----------------|------------------------------------------------------| -------------
|
||||
Alibaba Cloud | [ACK](../end-user/components/cloud-services/terraform/alibaba-ack) | Terraform configuration for Alibaba Cloud ACK cluster
|
||||
| | [EIP](../end-user/components/cloud-services/terraform/alibaba-eip) | Terraform configuration for Alibaba Cloud EIP
|
||||
| | [OSS](../end-user/components/cloud-services/terraform/alibaba-oss) | Terraform configuration for Alibaba Cloud OSS
|
||||
| | [RDS](../end-user/components/cloud-services/terraform/alibaba-rds) | Terraform configuration for Alibaba Cloud RDS
|
||||
| | [Redis](../end-user/components/cloud-services/terraform/alibaba-redis) | Terraform configuration for Alibaba Cloud Redis
|
||||
| | [VPC](../end-user/components/cloud-services/terraform/alibaba-vpc) | Terraform configuration for Alibaba Cloud VPC
|
||||
| Azure | [Mariadb](../end-user/components/cloud-services/terraform/azure-database-mariadb) | Terraform configuration for Azure Database Mariadb
|
||||
| | [Storage Account](../end-user/components/cloud-services/terraform/azure-storage-account) | Terraform configuration for Azure Storage Account
|
||||
| AWS | [S3](../end-user/components/cloud-services/terraform/aws-s3) | Terraform configuration for AWS S3 bucket
|
||||
| Orchestration Type | Cloud Provider | Cloud Resource | Description |
|
||||
|--------------------|----------------|------------------------------------------------------------------------------------------|-----------------------------------------------------------------------|
|
||||
| Terraform | Alibaba Cloud | [ACK](../end-user/components/cloud-services/terraform/alibaba-ack) | Terraform configuration for Alibaba Cloud ACK cluster |
|
||||
| | | [ASK](../end-user/components/cloud-services/terraform/alibaba-ask) | Terraform configuration for Alibaba Cloud Serverless Kubernetes (ASK) |
|
||||
| | | [EIP](../end-user/components/cloud-services/terraform/alibaba-eip) | Terraform configuration for Alibaba Cloud EIP |
|
||||
| | | [OSS](../end-user/components/cloud-services/terraform/alibaba-oss) | Terraform configuration for Alibaba Cloud OSS |
|
||||
| | | [RDS](../end-user/components/cloud-services/terraform/alibaba-rds) | Terraform configuration for Alibaba Cloud RDS |
|
||||
| | | [Redis](../end-user/components/cloud-services/terraform/alibaba-redis) | Terraform configuration for Alibaba Cloud Redis |
|
||||
| | | [SLS Project](../end-user/components/cloud-services/terraform/alibaba-sls-project) | Terraform configuration for Alibaba Cloud SLS Project |
|
||||
| | | [SLS Store](../end-user/components/cloud-services/terraform/alibaba-sls-store) | Terraform configuration for Alibaba Cloud SLS Store |
|
||||
| | | [VPC](../end-user/components/cloud-services/terraform/alibaba-vpc) | Terraform configuration for Alibaba Cloud VPC |
|
||||
| | | [VSwitch](../end-user/components/cloud-services/terraform/alibaba-vswitch) | Terraform configuration for Alibaba Cloud VSwitch |
|
||||
| | AWS | [S3](../end-user/components/cloud-services/terraform/aws-s3) | Terraform configuration for AWS S3 bucket |
|
||||
| | Azure | [Mariadb](../end-user/components/cloud-services/terraform/azure-database-mariadb) | Terraform configuration for Azure Database Mariadb |
|
||||
| | | [Storage Account](../end-user/components/cloud-services/terraform/azure-storage-account) | Terraform configuration for Azure Storage Account |
|
||||
|
||||
## Creating your cloud service
|
||||
|
||||
First [create an application](../how-to/dashboard/application/create-application). Please choose the type of your cloud service,
|
||||
which has a prefix of `aws-`, `azure` or `alibaba-`.
|
||||
which has a prefix of `aws-`, `azure`, `alibaba-` or `tencent-`.
|
||||
|
||||
For different vendors, these parameters update accordingly.
|
||||
|
||||
|
|
|
|||
|
|
@ -177,7 +177,7 @@
|
|||
},
|
||||
{
|
||||
"type": "doc",
|
||||
"id": "version-v1.2/end-user/components/cloud-services/provider-and-consume-cloud-services"
|
||||
"id": "version-v1.2/end-user/components/cloud-services/provision-and-consume-cloud-services"
|
||||
},
|
||||
{
|
||||
"type": "doc",
|
||||
|
|
|
|||
Loading…
Reference in New Issue