Description:
To simplify the deployment of the application in Kubernetes, it would be helpful to configure Celery dynamically using environment variables.
The advantage: You don't need to modify configuration.py to change values like broker URL, result backend, or timeouts for specific environments. Instead, these values can be set directly in the Kubernetes manifest or via ConfigMap/Secret.
Reference:
A description of a possible implementation can be found in the following blog article: Celery Config Env Vars