kajanajustin opened a new issue, #34561: URL: https://github.com/apache/airflow/issues/34561
### Official Helm Chart version 1.10.0 (latest released) ### Apache Airflow version 2.6.2 ### Kubernetes Version 1.24 ### Helm Chart configuration ``` # Configuration for the redis provisioned by the chart redis: enabled: true terminationGracePeriodSeconds: 600 # Create ServiceAccount serviceAccount: # Specifies whether a ServiceAccount should be created create: true # The name of the ServiceAccount to use. # If not set and create is true, a name is generated using the release name name: ~ # Annotations to add to worker kubernetes service account. annotations: {} persistence: # Enable persistent volumes enabled: true # Volume size for worker StatefulSet size: 1Gi # If using a custom storageClass, pass name ref to all statefulSets here storageClassName: # Annotations to add to redis volumes annotations: {} resources: {} # limits: # cpu: 100m # memory: 128Mi # requests: # cpu: 100m # memory: 128Mi # If set use as redis secret. Make sure to also set data.brokerUrlSecretName value. passwordSecretName: ~ # Else, if password is set, create secret with it, # Otherwise a new password will be generated on install # Note: password can only be set during install, not upgrade. password: ~ # This setting tells kubernetes that its ok to evict # when it wants to scale a node down. safeToEvict: true # Select certain nodes for redis pods. nodeSelector: {} affinity: nodeAffinity: requiredDuringSchedulingIgnoredDuringExecution: nodeSelectorTerms: - matchExpressions: - key: kubernetes.io/os operator: In values: - linux - key: kubernetes.io/arch operator: In values: - arm64 tolerations: [] topologySpreadConstraints: [] # Set to 0 for backwards-compatiblity uid: 0 # If not set, `redis.uid` will be used securityContext: {} # runAsUser: 999 # runAsGroup: 0 # Detailed default security context for redis for container and pod level securityContexts: pod: {} container: {} podAnnotations: {} # Auth secret for a private registry # This is used if pulling airflow images from a private registry registry: secretName: ~ # Example: # connection: # user: ~ # pass: ~ # host: ~ # email: ~ connection: {} ``` values.yaml specific redis section ### Docker Image customizations No edits or customizations to Dockerfile using the official one from the `310865762107.dkr.ecr.us-east-1.amazonaws.com/apache/airflow` and `310865762107.dkr.ecr.us-east-1.amazonaws.com/redis` 7-bullseye ### What happened _No response_ ### What you think should happen instead _No response_ ### How to reproduce Set up a new cluster install helm chart version 1.10.0 for airflow, and just set enable Redis to true. It should work with no problem but instead, I get errors such as on the worker pod and the flower pod ``` ERROR/MainProcess] consumer: Cannot connect to redis://:**@airflow-redis:6379/0: invalid username-password pair or user is disabled..Trying again in 20.00 seconds... (10/100)[2023-09-22 15:33:43,436: ERROR/MainProcess] consumer: Cannot connect to redis://:**@airflow-redis:6379/0: invalid username-password pair or user is disabled..Trying again in 22.00 seconds... (11/100)[2023-09-22 15:34:05,480: ERROR/MainProcess] consumer: Cannot connect to redis://:**@airflow-redis:6379/0: invalid username-password pair or user is disabled..Trying again in 24.00 seconds... (12/100) ``` And ``` File "/home/airflow/.local/lib/python3.7/site-packages/kombu/connection.py", line 450, in _reraise_as_library_errors raise ConnectionError(str(exc)) from exckombu.exceptions.OperationalError: invalid username-password pair or user is disabled. ``` ### Anything else Occurs everytime, need to know what i am doing wrong with my values.yaml ### 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