On the top navigation bar, click Business Apps, and then select ConfigMaps from the App Management menu.
On the ConfigMaps tab, click Add ConfigMap.
Configure ConfigMap parameters as needed, and then click OK.
Table-1 Configuring ConfigMap parameters
Parameter |
Description |
Name |
Enter a name for the ConfigMap. |
Version |
Enter a version number. |
Cluster |
Select a container cluster. The cluster must be the one where applications to use this ConfigMap will be deployed. You can select a shared cluster, exclusive cluster, or MCP cluster. |
Application Group |
Select an application group. The application group must contain the applications to use this ConfigMap. |
Description |
Enter a description. |
Labels |
Configure labels. The labels are used for managing ConfigMaps. |
Data |
A ConfigMap defines the data used in applications through key-value pairs, which are mounted in applications in the form of a catalog. A key corresponds to a file name, and a value corresponds to the file content. The directory path must be specified when an application is created.
|
On the top navigation bar, click Business Apps, and then select ConfigMaps from the App Management menu.
On the Secrets tab, click Add Secret.
Configure secret parameters as needed, and then click OK.
Table-2 Configuring secret parameters in a visual mode
Parameter |
Description |
Name |
Enter a name for the secret. |
Cluster |
Select a container cluster. The cluster must be the one where applications to use this secret will be deployed. |
Application Group |
Select an application group. The application group must contain the applications to use this secret. |
Tags |
Configure tags. The tags are used for managing secrets. |
Tag Creation |
The secret key used in applications is defined through key-value pairs, which are mounted in applications in the form of a catalog. A key corresponds to a file name, and a value corresponds to the file content. The directory path must be specified when an application is created.
|
Auto Transcoding |
Select whether to automatically encode the secret data by using Base64. If you do not enable auto transcoding, you must enter the secret data that has been encoded by using Base64. |
Table-3 Configuring secret parameters in YAML mode
Parameter |
Description |
Cluster |
Select a container cluster. The cluster must be the one where applications to use this secret will be deployed. |
Application Group |
Select an application group. The application group must contain the applications to use this secret. |
Select File |
Click Browse to upload a TXT, CONF, or YAML file not larger than 1 MB. Use the key as the file name, and enter the value of the key in the file. For the format of the file content, see "YAML secret deployment example." |