Managing Configuration Items

Prerequisites

• A CCE cluster has been bound to the environment. For details, see Binding a CCE Cluster.
• The namespace to which the configuration item belongs has been bound. For details, see Binding a Namespace.

Creating a Configuration Item

1. Log in to ServiceStage.
2. Choose Environment Management. The Environment Management page is displayed.
3. Click the target environment. The Overview page is displayed.
4. Choose Cloud Container Engine from Compute.
5. Go to the ConfigMap page.
   • For a non-HA environment, click the ConfigMap tab.
   • For an HA environment, click the bound CCE cluster and click the ConfigMap tab.

6. Click Create Configuration Item.
   ServiceStage allows you to create configuration items in Visualization or YAML mode.

   • Method 1: Visualization
     Configure the configuration item by referring to Table 1. Parameters marked with an asterisk (*) are mandatory.

     Table 1 Parameters for creating a configuration item in visualization mode

     Parameter	Description
     *Configuration Name	Configuration item name, which must be unique in a namespace. Enter 4 to 24 characters. Start with a lowercase letter and end with a lowercase letter or digit. Only use lowercase letters, digits, and hyphens (-).
     *Cluster	Cluster where the configuration item will be used.
     *Namespace	Namespace to which the configuration item belongs.
     Description	Configuration item description. Enter 0 to 255 characters.
     Configuration Data	Configuration data to be used in applications or used to store configuration data. Key indicates a file name, and Value indicates the content in the file. Click Add Data. Enter the key and value. The key contains 1 to 63 characters. Only use digits, letters, dots (.), hyphens (-), and underscores (_). The value contains 0 to 1,048,576 characters.
     Configuration Labels	Labels that you want to attach to various objects (such as applications, nodes, and services) in the form of key-value pairs. Labels define the identifiable attributes of these objects and are used to manage and select the objects. Click Add. Enter the key and value. The key contains 1 to 63 characters. Start and end with a letter or digit. Only use digits, letters, dots (.), hyphens (-), underscores (_), and slashes (/). The value contains 1 to 63 characters. Start and end with a letter or digit. Only use digits, letters, dots (.), hyphens (-), and underscores (_).

     Figure 1 Setting configuration item parameters in Visualization mode
     
   • Method 2: YAML
     NOTE:

     To create a configuration item by uploading a file, ensure that a configuration item resource file in YAML format has been created and the file size is less than 1 MB. For details, see Requirements for the Configuration Item Resource File.

     1. Select a cluster from the Cluster drop-down list.
     2. Use either of the following methods to set the configuration item resource file:
        • Click Upload File, select the configuration item resource file created locally, click Open, and wait until the file is uploaded.
        • Write or modify the ConfigMap resource file in Orchestration content.
     Figure 2 Setting configuration item parameters in YAML mode
     

7. Click Create ConfigMap.

   After the configuration item is created, it is displayed in the configuration item list.

Follow-up Operations

After a configuration item is created, you can search for, view, update, and delete the configuration item by referring to Table 2.

NOTICE:

• After a configuration item is deleted, the component to which the configuration item is mounted or referenced in environment variables may fail to be started after being upgraded.
• System configuration items can only be viewed.

Requirements for the Configuration Item Resource File

A configuration item resource file should be in YAML format, and the file size cannot exceed 1 MB.

Example:

apiVersion: v1
data: {}
kind: ConfigMap
metadata:
  annotations:
    description: ''
  labels: {}
  name: configmap-ww8qkl
  namespace: cse

For details about key parameters, see Table 3.