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

   ### Official Helm Chart version
   
   1.10.0
   
   ### Apache Airflow version
   
   2.6.2
   
   ### Kubernetes Version
   
   1.28.2
   
   ### Helm Chart configuration
   
   airflow:
     legacyCommands: false
     image:
       repository: apache/airflow
       tag: 2.6.2
   
     executor: KubernetesExecutor
   
     config:
       AIRFLOW__WEBSERVER__EXPOSE_CONFIG: "False"
       AIRFLOW__CORE__LOAD_EXAMPLES: "False"
   
     variables: []
   
     pools: []
   
     extraPipPackages: []
   
   
   scheduler:
     replicas: 1
   
   
   web:
     replicas: 1
     service:
       type: ClusterIP
       externalPort: 8080
   
   workers:
     replicas: 1
     persistence:
       enabled: false
       storageClassName: efs-sc
       size: 10Gi
   
   
   flower:
     enabled: false
   
   logs:
     persistence:
       enabled: false
   
   dags:    
     gitSync:
       enabled: true
       repo: 
https://git-codecommit.cn-northwest-1.amazonaws.com.cn/v1/repos/****
       branch: airflow
       credentialsSecret: airflow-credentials-secret
   
   extraSecrets:
     airflow-credentials-secret:
       data: |
         GIT_SYNC_USERNAME:***********
         GIT_SYNC_PASSWORD: *******************
   
   ingress:
     enabled: false
   
   
   postgresql:
     enabled: true
     persistence:
       enabled: true
       storageClass: efs-sc
       size: 8Gi
   
   redis:
     enabled: True
     persistence:
       enabled: true
       storageClassName: efs-sc
       size: 8Gi
   
   triggerer:
     enabled: true
     replicas: 1
     persistence:
       enabled: true
       storageClassName: efs-sc
       size: 10Gi
   
   
   ### Docker Image customizations
   
   _No response_
   
   ### What happened
   
   I used helm to install airflow in AWS EKS. After executing the install 
command, the postgreSQL pod remained in a CrashLoopBackOff state. I used the 
kubectl logs command to check the pod log and found no abnormalities. The 
detailed information is as follows
   
![image](https://github.com/apache/airflow/assets/122849336/1278d14e-086b-429a-a69a-9af48e6f5510)
   
   PostgreSQL was unable to start properly, causing my other pods' wait for air 
flow migrations (init) container to fail. His log error was that the postgreSQL 
service could not be queried, which resulted in most of my pods being in an 
initialization state
   
![image](https://github.com/apache/airflow/assets/122849336/674fbb07-d241-4db5-8486-3e5e05a1a00c)
   
   
   ### What you think should happen instead
   
   I don't know why it caused the pods of PostgreSQL to continue to 
CrashLoopBackOff. The persistent storage I configured for him uses AWS's EFS
   
   ### How to reproduce
   
   Configure EFS persistent storage using AWS eks 1.28 version, and then 
execute install with my value.yaml file to reproduce
   
   ### 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