Configuring Config Maps and Secrets


This section shows how the application developer can create new config maps and secrets to inject configuration information into the container.


Config maps can be used to store fine-grained information such as a single attribute, or coarse-grained information such as an entire profile or a JSON object. The config map can store key/value pair configuration data that can be used in pods. With config maps, it is easier to process strings that do not contain sensitive information.


Secrets are helpful for addressing the configuration of sensitive data such as passwords, tokens, and keys without exposing these sensitive data to images or pod specs. A secret can be used as a Volume or as an environment variable. With secrets, it is easier to process strings that contain sensitive information.

Prerequisites

Cluster and namespace name are selected.

Creating a Config Map

  1. In the EnOS Management Console, navigate to Enterprise Container Platform and select Configuration > Config Maps.

  2. Click the New Config Map button to complete the configuration information.


The steps to configuring config maps in Container Cluster Management are similar to those in Developer Studio. For more information, see Configuring Config Maps and Secrets.

Creating a Secret

  1. Select Configuration > Secrets.

  2. Click the New Secret button to complete the configuration information.


The steps to configuring config secrets in Container Cluster Management are similar to those in Developer Studio. For more information, see Configuring Config Maps and Secrets.

Next Step

After the config map and secret are created, you can clone, edit, and delete them as needed. The specific steps are similar to those for Configuring Deployments.