Skip to main content

Configs

You can add Secret or ConfigMap objects to your projects. These configurations are mounted like a disk to your container when running the application. To view existing configurations or define a new configuration, go to the "Configs" section from the project menu.

On this page, you can edit or delete previous configurations if you no longer need them. Also, by clicking on the "Add a Config" button, you can create a Secret or ConfigMap in this project. This section allows you to choose from Secret types such as Source, Image, Generic, and Webhook, as well as ConfigMap.

Generic​

This configuration is used to store small sensitive data such as passwords, OAuth tokens, or SSH keys.

To define a Generic Secret, you need to enter the following information:

  • Name

    A unique name (at the project or Namespace level) which is equivalent to metadata.name in Kubernetes.

  • Key

    The Secret key corresponding to the Key section in data or stringData in Kubernetes.

  • Value

    The Secret value corresponding to the Value section in data or stringData in Kubernetes. This parameter can be entered as text or in the form of a file.

Image​

This configuration is designed to store credentials required to access private registries. In Kubernetes, when a pod needs to pull an image from a private registry, it uses this configuration.

To define an Image Secret, you can choose between two authentication types:

Image Registry Credential​

In this mode, you can separately enter the necessary information in each section:

  • Registry URL

    The URL of the image registry.

  • Username

    The username for accessing the registry.

  • Password

    The password for accessing the registry.

Configuration File​

In this mode, you enter the entire Docker configuration file as JSON.

![](https://arvandocsen.s3.ir-thr-at1.arvanstorage.ir/caas/manage-app/configs/image-conf.png)

Source​

This configuration is for storing source credentials such as SSH keys or tokens for accessing repositories like GitHub or GitLab.

SSH Key​

In this mode, you enter the SSH key for accessing private repositories.

![](https://arvandocsen.s3.ir-thr-at1.arvanstorage.ir/caas/manage-app/configs/source-key.png)

To define this configuration, you need to enter the following information:

  • Name

    A unique name (at the project or Namespace level) which is equivalent to metadata.name in Kubernetes.

  • SSH Key

    The private SSH key for accessing the Git repository.

  • Use Custom gitconfig File

    The gitconfig file determines the Git settings, which can include user information, aliases for Git commands, etc.

Webhook​

Webhook Secrets are used to secure webhooks in Kubernetes. Webhooks are HTTP callbacks used to automatically start a process like CI/CD or a notification.

![](https://arvandocsen.s3.ir-thr-at1.arvanstorage.ir/caas/manage-app/configs/webhook.png)

In this configuration, a token or key is placed to verify the origin of the request to ensure its authenticity.

To define a Webhook Secret, you need to enter the following information:

  • Name

    A unique name (at the project | Namespace level) which is equivalent to metadata.name in Kubernetes.

  • Key

    The key used in validating incoming webhooks.

ConfigMap​

Unlike Secrets, ConfigMaps are used to store non-sensitive data in key/value pairs. These data can be configuration files or command-line arguments.

![](https://arvandocsen.s3.ir-thr-at1.arvanstorage.ir/caas/manage-app/configs/confug-map.png)

To define a ConfigMap, you need to enter the following information:

  • Name

    A unique name (at the project or Namespace level) which is equivalent to metadata.name in Kubernetes.

  • Key

    The ConfigMap key corresponding to the Key section in data or binaryData in Kubernetes.

  • Value

    The ConfigMap value corresponding to the Value section in data or binaryData in Kubernetes. This parameter can be entered as text or in the form of a file.