Custom Object Storage
To set up custom object storage for production deployment, you need to modify the server environment variables in the values.yaml
file. Add or update the variables listed below under the environment
section of the server configuration.
Environment Variables for Custom Object Storage
Name | Type | Description | Default | Required |
---|---|---|---|---|
S3_ACCESS_KEY | String | Access key for the S3 storage. | Yes | |
S3_SECRET_KEY | String | Secret key for the S3 storage. | Yes | |
S3_END_POINT | String | Endpoint URL for the S3-compatible storage. | Yes | |
S3_BUCKET | String | Name of the S3 bucket where files will be stored. | Yes | |
S3_PORT | Number | Port to connect to the S3 storage. | Yes | |
S3_REGION | String | The region of your S3 bucket (required if using AWS S3). | us-east-1 | No |
S3_USE_SSL | Boolean | Enable or disable SSL for connections to the S3 storage. | true | No |
S3_IS_AWS_S3 | Boolean | Specify if the S3 storage is AWS S3. | false | No |
S3_CREATE_BUCKET_IF_NOT_EXIST | Boolean | Automatically create the bucket if it does not exist. | true | No |
S3_USE_PRE_SIGNED_URL | Boolean | Use pre-signed URLs to offload bandwidth by allowing direct file access from S3. Note: Enabling this requires your end users to have network access to the S3 instance to use the pre-signed URL. | true | No |
Note: You may not find all the above variables already defined in the
values.yaml
file. Add or update them as necessary under theserver.environment
section to configure custom object storage for your deployment.