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

   ### Official Helm Chart version
   
   1.10.0
   
   ### Apache Airflow version
   
   2.6.2
   
   ### Kubernetes Version
   
   1.21.6
   
   ### Helm Chart configuration
   
   ```
   logs:
     persistence:
       # Enable persistent volume for storing logs
       enabled: true
       # Volume size for logs
       #size:  5Gi
       # Annotations for the logs PVC
       #annotations: {}
       # If using a custom storageClass, pass name here
       #storageClassName:
       ## the name of an existing PVC to use
       existingClaim: airflow-logs-pvc-dlu #airflow-logs-pvc-test-v1 
#airflow-logs-test
   ```
   
   KubernetesPodOperator:
   `startup_timeout_seconds=300`
   
   ### Docker Image customizations
   
   _No response_
   
   ### What happened
   
   When I run with logs not enabled it all works fine
   
   When the logs are enabled:
   At the beginning all works well and the logs are available, but after 
sometime (hours) the logs volumes can not be mounted into the pod  of the 
cronjob of the kubernetes pod operator until it finally timeouts.
   
![image](https://github.com/apache/airflow/assets/32225250/5fd7a7e0-b033-459e-9614-41e0c39cfa43)
   
   - I have check that the volume does not have a bottleneck (cpu, mem, iops...)
   - This volume is not an issue on any other deployment on the cluster
   
   ### What you think should happen instead
   
   _No response_
   
   ### How to reproduce
   
   I am currently using portworx volumes
   
   ### Anything else
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [ ] 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