Configuration
The installation can be customized and configured using Helm values.
The complete list of available configuration keys and their descriptions is available in the official Helm repository at the following URL:
Velero Helm Chart Configuration
Below are some notes on specific configuration parameters.
ORIGINS
Helm key: apiConfig.origins*
You can define up to 100 allowed origins that should be permitted to make cross-origin requests.
An origin is the combination of:
- Protocol (e.g.,
http,https) - Domain (e.g.,
myapp.com,localhost) - Port (e.g.,
80,443,8001)
SECURITY TOKEN KEY
Helm key: apiConfig.securityTokenKey
The security token key is generated automatically. However, if you want to specify and persist it across updates, you can generate it manually using the following command:
To generate a fixed secure random secret key use the command:
openssl rand -hex 32
If no secret key is provided, the system regenerates new missed keys itself each time it is restarted.
API RATE LIMITER
The backend supports custom API rate limiters. The default rate limiter is defined by the key API_RATE_LIMITER_L1.
You can define up to 100 custom rate limiters, from the key API_RATE_LIMITER_CUSTOM_L1 to API_RATE_LIMITER_CUSTOM_L99. Rules can be applied to:
- A tag (e.g., Security, Info, Backup, Schedule, etc.)
- A specific endpoint (e.g., backup/update-expiration, utils/version, etc.)
Replace the characters \ - in endpoint urls with the _
The description field of each endpoint describes the key to configure the customized rate limiter and the actual setup.
Example : if we want to create a rule for the specific endpoint "/backup/get-storage-classes" (tag: Backup) it will be: Backup:backup_get_storage_classes:60:600