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

   ### Official Helm Chart version
   
   1.8.0 (latest released)
   
   ### Apache Airflow version
   
   2
   
   ### Kubernetes Version
   
   1.25
   
   ### Helm Chart configuration
   
   _No response_
   
   ### Docker Image customizations
   
   _No response_
   
   ### What happened
   
   Running the standard install on my kubernetes cluster doesn't create the 
required peristent volumes to bind to the persistent volume claims. 
   I ran:
   ```helm upgrade --install airflow apache-airflow/airflow --namespace airflow 
--create-namespace```
   Describing the resources yeilds:
   ```
   > kubectl -n airflow get pods
   NAME                                   READY   STATUS              RESTARTS  
 AGE
   airflow-postgresql-0                   0/1     Pending             0         
 8s
   airflow-redis-0                        0/1     Pending             0         
 8s
   airflow-run-airflow-migrations-9cccj   0/1     ContainerCreating   0         
 8s
   airflow-scheduler-8579dd79df-w2lq4     0/2     Init:0/1            0         
 8s
   airflow-statsd-5b4964646f-887pt        0/1     Running             0         
 8s
   airflow-triggerer-79677ff998-6x4tv     0/1     Init:0/1            0         
 8s
   airflow-webserver-6c595fcb6d-2bjnm     0/1     Init:0/1            0         
 8s
   airflow-worker-0                       0/2     Pending             0         
 8s
   > kubectl -n airflow get pvc
   NAME                        STATUS    VOLUME   CAPACITY   ACCESS MODES   
STORAGECLASS   AGE
   data-airflow-postgresql-0   Pending                                          
           18s
   logs-airflow-worker-0       Pending                                          
           18s
   redis-db-airflow-redis-0    Pending                                          
           18s
   > kubectl -n airflow get pv
   No resources found
   ```
   The system will remain in this state, with redis, postgres, and workers 
failing to create with the status:
   ```  Warning  FailedScheduling  15s    default-scheduler  0/1 nodes are 
available: 1 pod has unbound immediate PersistentVolumeClaims. preemption: 0/1 
nodes are available: 1 Preemption is not helpful for scheduling.```
   
   When I describe the persistent cliams I get:
   ```
   > kubectl -n airflow describe pvc data-airflow-postgresql-0
   Name:          data-airflow-postgresql-0
   Namespace:     airflow
   StorageClass:
   Status:        Pending
   Volume:
   Labels:        app.kubernetes.io/component=primary
                  app.kubernetes.io/instance=airflow
                  app.kubernetes.io/name=postgresql
   Annotations:   <none>
   Finalizers:    [kubernetes.io/pvc-protection]
   Capacity:
   Access Modes:
   VolumeMode:    Filesystem
   Used By:       airflow-postgresql-0
   Events:
     Type    Reason         Age                From                         
Message
     ----    ------         ----               ----                         
-------
     Normal  FailedBinding  2s (x42 over 10m)  persistentvolume-controller  no 
persistent volumes available for this claim and no storage class is set
   ```
   
   ```
   > kubectl -n airflow describe pvc logs-airflow-worker-0
   Name:          logs-airflow-worker-0
   Namespace:     airflow
   StorageClass:
   Status:        Pending
   Volume:
   Labels:        component=worker
                  release=airflow
                  tier=airflow
   Annotations:   <none>
   Finalizers:    [kubernetes.io/pvc-protection]
   Capacity:
   Access Modes:
   VolumeMode:    Filesystem
   Used By:       airflow-worker-0
   Events:
     Type    Reason         Age                 From                         
Message
     ----    ------         ----                ----                         
-------
     Normal  FailedBinding  76s (x42 over 11m)  persistentvolume-controller  no 
persistent volumes available for this claim and no storage class is set
   ```
   
   ```
   > kubectl -n airflow describe pvc redis-db-airflow-redis-0
   Name:          redis-db-airflow-redis-0
   Namespace:     airflow
   StorageClass:
   Status:        Pending
   Volume:
   Labels:        component=redis
                  release=airflow
                  tier=airflow
   Annotations:   <none>
   Finalizers:    [kubernetes.io/pvc-protection]
   Capacity:
   Access Modes:
   VolumeMode:    Filesystem
   Used By:       airflow-redis-0
   Events:
     Type    Reason         Age                   From                         
Message
     ----    ------         ----                  ----                         
-------
     Normal  FailedBinding  2m10s (x42 over 12m)  persistentvolume-controller  
no persistent volumes available for this claim and no storage class is set
   ```
   
   ### What you think should happen instead
   
   Airflow should create persistent volumes to bind to the appropriate claims. 
   
   ### How to reproduce
   
   The issue doesn't happen in Minikube, so not sure how to reproduce without 
access to my home Kubernetes. I have successfully provisioned persistent 
volumes and claims for other services, which run successfully in the same 
cluster. 
   
   Best I can do is to [install the Rancher 
kubernetes](https://docs.rke2.io/install/quickstart) and follow the same 
install steps from above.
   
   ### Anything else
   
   This happens every time I try to install the chart. I've also tried hacking 
it by creating volumes for the claims to bind to, but the claims don't bind to 
them.
   
   ### 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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to