Environment variables and configuration volumes
Environment Variables
Add the environment variables here. These will be available to the container at runtime.
You can mark the value as a secret by clicking the "Lock" icon.
Secret values are stored in a secure vault at Kapstan.
Upload .env file:
- You can add multiple environment variables by uploading a ".env" file.
- The file should be in the format of key-value pairs. E.g.,
DB_HOST=localhost
DB_PORT=3306
Download .env file: You can download all of your environment variables (key-value pair) by clicking on the download icon at the top right corner. Note that secret values will not be downloaded.
Configuration volumes
Configuration volumes are used to define variables, similar to environment variables. These are recommended to store large textual values. Typically, volumes are used for SSL certs, private keys, or tokens. You can have multiple volumes per container. The path of the volume becomes the key, and file content becomes the value of the variable. A volume has the following configuration variables:
- Config File: First upload the configuration (value) file.
- Stored as a secret: Tick this if you like your value to be stored as base64 encoded.
- Hardcoded Path: Provide a path to the volume. E.g.,
/temp/config - Name of the Volume: A meaningful name to identify the volume.
To create a configuration volume, go to Configuration volumes sub-tab under Config tab of an application, upload a configuration file and fill in the details. Click on "Save" to create the volume.
Kapstan uses Kubernetes in-built Secrets to store secret volumes. The data is not secured but just obfuscated. The recommended way of storing secrets is to use secret-type environment variables.
