Creating a Kubernetes Environment in Resource Management Mode
Before Creating and Deploying a Component Based on a Container Using UI Configurations, Creating and Deploying a Component Based on a Container Using YAML Configurations, and Creating a Component by Importing a CCE Workload, you need to create a Kubernetes environment.
Creating a Kubernetes Environment in Resource Management Mode
- Log in to ServiceStage.
- Choose Environment Management > Create Environment.
- Configure the basic environment information by referring to the following table. Parameters marked with an asterisk (*) are mandatory.
Parameter
Description
*Environment
Unique environment name.
Enter 2 to 64 case-insensitive characters. Start with a letter and end with a letter or digit. Only use letters, digits, underscores (_), and hyphens (-).
*Enterprise Project
Enterprise projects let you manage cloud resources and users by project.
It is available after the function is enabled. For details, see Enabling the Enterprise Project Function.
- Click the drop-down list to select an existing enterprise project.
- Click Create Enterprise Project to create an enterprise project and select it. For details, see Creating an Enterprise Project.
*Environment Type
Select Kubernetes. It is applicable to container-based deployment (CCE). Components are deployed using container images and scheduled by Kubernetes.
*HA Environment
- Yes: Create an HA environment of the Kubernetes type to provide intra-city active-active HA capabilities for applications. This environment is applicable for deploying applications that require intra-city HA.
- No: Create a non-HA environment of the Kubernetes type to deploy applications that do not require intra-city HA.
*AZ
Select two AZs for the environment when High Available is set to OK.
*VPC
NOTICE:After the environment is created, the VPC cannot be modified during Modifying an Environment.
Select the VPC where the environment resource is located based on your service requirements.
VPC where the environment resources are located.
- To use a created VPC, select a VPC created under the current account from the drop-down list.
- To use a shared VPC, select a VPC that another account shares with the current account from the drop-down list.
VPC owners can share the subnets in a VPC with one or multiple accounts through Resource Access Manager (RAM). Through VPC sharing, you can easily configure and manage multiple accounts' resources at low costs. For more information about VPC and subnet sharing, see VPC Sharing.
- To use a new VPC, click Create a VPC. For details, see Creating a VPC.
Environment Tag
Tags are used to identify cloud resources. When you have multiple cloud resources of the same type, you can use tags to classify them based on usage, owner, or environment.
If your organization has configured tag policies for ServiceStage, add tags to trackers based on the policies. If a tag does not comply with the tag policies, environment creation may fail. Contact your administrator to learn more about tag policies.
Each environment can have a maximum of 20 tags.- Click Add Tag. The Add Tag dialog box is displayed.
- Click Add Tag.
- Enter the key and value of the tag.
- The key contains 1 to 36 characters, including digits, letters, underscores (_), or hyphens (-).
- The value contains 2 to 43 characters, including digits, letters, underscores (_), periods (.), or hyphens (-).
It is recommended that you create a predefined tag on TMS to add the same tag to different resources.
- Click OK.
Description
Environment description. Enter up to 128 characters.
*Configuration Mode
Click Resource management to manage created basic resources in the environment.
- Click Create Now.
Follow-up Operations
- Managing CCE Resources: After a Kubernetes environment is created, bind a CCE cluster to the environment and manage the cluster before using the environment to deploy components.
- Managing Basic Resources: After an environment is created, other basic resources (excluding CCE clusters) need to be managed in the environment to form an environment.
- Removing Managed Basic Resources: Remove managed resources (except CCE clusters) that are no longer used.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot