Configuring Subnets

Constraints

• The subnets configured for the namespace are specified by both spec.custom.subnet_id and spec.custom.subnets configured in the add-on YAML file.
• If you need to delete a subnet, you cannot delete spec.custom.subnet_id. You must use another subnet to replace it.

Adding Subnets for a Namespace

By default, the CCI namespace associated with the CCE Cloud Bursting Engine for CCI add-on uses the subnet selected during the add-on installation. If you want to use other subnets, take the following steps:

1. Log in to the CCE console.
2. Click the name of the target CCE cluster to go to the cluster Overview page.
3. In the navigation pane, choose Add-ons.
4. Select the CCE Cloud Bursting Engine for CCI add-on and click Edit.
5. Click Edit YAML.
6. Configure the array of subnets in spec.custom. subnetID indicates the ID of each IPv4 subnet in the VPC of the CCE cluster, expect the default IPv4 subnet.

   The following is an example:

       custom:
         subnet_id: 11c2a970-xxxx-xxxx-xxxx-dfxxxxxxxx7d
         subnets: [
         {
               "subnetID": "efd70252-xxxx-xxxx-xxxx-72xxxxxxxxde"
         },
         {
               "subnetID": "55038f35-xxxx-xxxx-xxxx-ecxxxxxxxx49"
         },
         {
               "subnetID": "99b2a9f5-xxxx-xxxx-xxxx-64xxxxxxxx5a"
         }
         ]

   Table 1 Parameter description

   Parameter	Mandatory	Type	Description
   subnet_id	Yes	String	Indicates the ID of the default IPv4 subnet selected during the add-on installation. The default subnet quantity is 1.
   subnets	No	Array of subnet	Indicates an array of subnets in a namespace.

   Table 2 Data structure of the subnets field

   Parameter	Mandatory	Type	Description
   subnetID	Yes	String	ID of each IPv4 subnet to be added

7. Click Submit. In the instance list of the add-on, if the instance status is Running, the add-on has been deployed and is functioning normally.