Integrating cloud service is the most frequent need in our daily development, varying from the Object storage, Cloud database to LoadBalancer, Cache, or search engine. Faster to load them save more time, meanwhile, to orchestrate different resources from multi-cloud is quite a pain point.
In this section, we introduce an example to show you how to deploy cloud services.
Has a cloud vendor account with proper access to your target cloud resources
Ensure your account has a sufficient balance
Connect to a Kubernetes cluster on this cloud vendor for hosting your cloud services
First, visit VelaUX (KubeVela Dashboard), switch to the tab
Addon, and click up addon
xxx stands for the cloud provider name. We support the following Addons:
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:
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
KubeVela supports the following types of resources and more later on:
|Orchestration Type||Cloud Provider||Cloud Resource||Description|
|Terraform||Alibaba Cloud||ACK||Terraform configuration for Alibaba Cloud ACK cluster|
|ASK||Terraform configuration for Alibaba Cloud Serverless Kubernetes (ASK)|
|EIP||Terraform configuration for Alibaba Cloud EIP|
|OSS||Terraform configuration for Alibaba Cloud OSS|
|RDS||Terraform configuration for Alibaba Cloud RDS|
|Redis||Terraform configuration for Alibaba Cloud Redis|
|SLS Project||Terraform configuration for Alibaba Cloud SLS Project|
|SLS Store||Terraform configuration for Alibaba Cloud SLS Store|
|VPC||Terraform configuration for Alibaba Cloud VPC|
|VSwitch||Terraform configuration for Alibaba Cloud VSwitch|
|AWS||S3||Terraform configuration for AWS S3 bucket|
|Azure||Mariadb||Terraform configuration for Azure Database Mariadb|
|Storage Account||Terraform configuration for Azure Storage Account|
First create an application. Please choose the type of your cloud service,
which has a prefix of
For different vendors, these parameters update accordingly.
aws-s3 has the following parameters:
azure-database-mariadb has the following parameters:
alibaba-rds has the following parameters:
All cloud resources have some common parameters.
- DeleteResource: Whether to delete the corresponding cloud service when the app is deleted
- ProviderRef: The Provider which is referenced by a cloud service
- Region: Region is cloud provider's region. It will override
Set the above parameters according to your needs to complete creating the application, and then deploy the application.
- Check the cloud instance list
Like other apps, cloud service apps also need to switch to the corresponding environment page to view instance information. By default, there are several targets in an environment, and the cloud service will generate a corresponding number of instances.
In the instance list, the instance name, status, resource type, and location are displayed. In the beginning, the name is empty, because the cloud service instance generation takes a certain amount of time, and the name will appear when the instance is generated normally.
- View the cloud resource in the console of the cloud provider
You can visit the instance in the console of the cloud provider. For example, you can check the name or console to visit it.
For example, you can check Alibaba Cloud RDS instance in https://console.aliyun.com.
- Check details and status of the cloud instance
Check the detail button to view the application details.
You will find that each instance generates a Secret resource, which generally records the service's access address and key information. Secret resources will be distributed to the cluster and Namespace where the target is located while the control cluster exists. Therefore, other applications in the same environment can directly use the resource in the environment variable to obtain the access address and key.
In the last section
Component Status, the health status and the message of the cloud service instance is displayed.
- The cloud service is always ProvisioningAndChecking and has no name
The creation of cloud services generally takes a certain amount of time. Please wait or enter the cloud vendor console to view the creation progress.