Shared Config Map

A ConfigMap is an object used to store non-confidential data in key-value pairs. Shared ConfigMaps can be added to container config maps.

---

Accessing Shared Config Maps

1. After logging into CHAI™, click on the project where you want to add shared config maps, then click Cruize.

   

   

2. Click on the blueprint version count on the blueprint card. After clicking the count, the blueprint versions page will be displayed, which contains a list of blueprint versions as shown in the image below.

   

3. Click on the View configurations kebab menu option or click on the blueprint version name to view blueprint configurations.

   

4. After clicking the above options, the blueprint configurations page will open. Then go to the Config Maps tab beside the deployments tab as shown in the image below.

   

---

Adding a New Config Map

1. Click the Add New Config Map button from the Config Map tab. A form will be displayed to add a config map as shown in the image below.

   

   

   Note: If the blueprint is created from a transform profile, the config maps from the transform profile will be populated here.

2. Add a config map by providing the following details:

   Field	Description
   Config Map name	Enter the config map name
   Referenced as	Default selected is "Env", change as applicable
   Input type	Select applicable input type (Text-based/File-based)
   Add Text/File Data	Based on input type, provide key values using text data or by uploading a file for the value
   Labels and Annotations	Optional - Add labels and annotations here

---

1. Config Map Name

Naming requirements: - Only lowercase alphanumeric characters, hyphens (-), or periods (.) are allowed - Must start and end with an alphanumeric character - Maximum 253 characters allowed - Name must be unique

---

2. Referenced As

There are two options for "Referenced as":

Env

• For Env, you can only provide text-based config map data

Volume Mount

• For Volume Mount, config map data can be provided using text-based or file-based input
• For Volume Mount, provide the following details:
  • Mount path: Enter the mount path, which should start with '/'
  • Sub path: Optional
  • Subpath key: Also optional, but if subpath is entered, you must provide a subpath key

---

3. Labels & Annotations

Click here to learn more about labels and annotations.

---

Important Note:
ConfigMap data can be provided either using text-based input or file-based input (file-based is only available for "Referenced as" Volume Mount).

---

Share Config Map with Containers

Shared config maps can be shared with containers.

Steps to Share a Config Map

1. Click the shareable icon from the actions column of the config map you want to share.

   

2. This will open a popup with a list of all containers from deployments added under the same blueprint, as shown in the image below.

   

3. A hierarchical list of deployments with containers will be shown in the popup. Select containers to share the config map with them, or to share with all containers under a deployment, select the deployment and all containers under that deployment will be selected.

4. After selecting containers, click the Share button. This will share the config map with the selected containers.

These shared config maps can be added to container config maps from containers.

For more details on Add Shared Config Maps, please refer to this section.

---

View Config Map Data

To view config map data and labels & annotations:

• Click the View (Eye) icon from the actions column in the config maps table as shown in the image below.

  

---

Edit Config Map

1. Click the Edit icon from the actions column in the config maps table to edit config map data as shown in the image below.

   

2. This will open a form with data to edit. After editing, click the Update button to save the changes.

   

---

Delete Config Map

To delete a config map:

• Click the Delete icon from the actions column of the config map as shown in the image below.

• This will remove the deleted config map.