Creating a VM + Kubernetes Environment in Resource Management Mode

Creating a VM + Kubernetes Environment in Resource Management Mode

1. Log in to ServiceStage.
2. Choose Environment Management > Create Environment and configure the basic environment information by referring to the following table. Parameters marked with an asterisk (*) are mandatory.

   Parameter	Description
   *Environment	Environment name, which must be unique in the same enterprise project. Enter 2 to 64 case-sensitive 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 VM + Kubernetes. Applicable to creating and deploying components based on VMs or containers in the same environment.
   *VPC	VPC where the environment resources are located. After the environment is created, the VPC cannot be modified during Editing an Environment. Select the VPC where the environment resource is located based on your service requirements. 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 with a Subnet.
   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 0 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.

3. Click Create Now.

   On the Overview page, you can perform environment management operations such as basic resource management by referring to Follow-up Operations.

Follow-up Operations

• Managing Cluster Resources: After an environment is created, bind a cluster to the environment for management before creating and deploying components in containers in this environment.
• Managing Basic Resources: After an environment is created, other basic resources (excluding clusters) need to be managed in the environment to form an environment.
• Managing VM Agents: After an environment is created, install the agent on the VMs managed by the environment before creating and deploying components on VMs in this environment. After the host nodes are managed, the management nodes can communicate with the host nodes.
• Managing Environment Variables of an Environment: Environment variables of an environment describe environment information and environment resource information, such as middleware credentials, connection information, and environment functions. You can use these variables to shield environment or resource differences, and switch components to different environments or run them using different cloud service resources without modification.
• Editing an Environment: Modify the name, enterprise project, and description of an environment.
• View Environment Details: View environment details at any time.