V0lantis opened a new issue, #29654:
URL: https://github.com/apache/airflow/issues/29654

   ### Official Helm Chart version
   
   1.8.0 (latest released)
   
   ### Apache Airflow version
   
   2.4.3
   
   ### Kubernetes Version
   
   v1.21.14-eks
   
   ### Helm Chart configuration
   
   ```
   data:
     resultBackendConnection:
       protocol: redis
       host: my.host.io
       port: 6379
       db: 1
   ```
   
   ### Docker Image customizations
   
   _No response_
   
   ### What happened
   
   ```
     Error: Failed to render chart: exit status 1: Error: values don't meet the 
specifications of the schema(s) in the following chart(s):
     airflow:
     - data.resultBackendConnection: pass is required
     - data.resultBackendConnection: sslmode is required
     - data.resultBackendConnection: Additional property password is not allowed
     Error: plugin "diff" exited with error
   ```
   
   ### What you think should happen instead
   
   As specified in Celery 
[documentation](https://docs.celeryq.dev/en/latest/userguide/configuration.html#redis-backend-settings),
 I shouldn't have any issue just passing a Url like 
   ```
   config:
     celery:
       result_backend: "redis://my.host.io:6379/1"
   ```
   
   Although when I am doing so, I have error in my DagProcessor:
   
   ```
   Liveness probe failed: You have configured a result_backend of 
redis://my.host.io:6379/1, it is highly recommended to use an alternative 
result_backend (i.e. a database). 
   No alive jobs found.                                   
   ````
   
   ### How to reproduce
   
   Just copy past my configuration
   
   ### Anything else
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [X] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscr...@airflow.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to