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

   ### Apache Airflow version
   
   main (development)
   
   ### What happened
   
   We keep on getting very frequent failures of Helm Chart tests and seems that 
a big number of those errors are because of errors when pulling charts from 
bitnami for postgres:
   
   Example here (but I saw it happening very often recently): 
   
   
https://github.com/apache/airflow/runs/6666449965?check_suite_focus=true#step:9:314
   
   ```
     Save error occurred:  could not find : chart postgresql not found in 
https://charts.bitnami.com/bitnami: looks like 
"https://charts.bitnami.com/bitnami"; is not a valid chart repository or cannot 
be reached: stream error: stream ID 1; INTERNAL_ERROR
     Deleting newly downloaded charts, restoring pre-update state
     Error: could not find : chart postgresql not found in 
https://charts.bitnami.com/bitnami: looks like 
"https://charts.bitnami.com/bitnami"; is not a valid chart repository or cannot 
be reached: stream error: stream ID 1; INTERNAL_ERROR
     Dumping logs from KinD
   ```
   
   It is not only a problem for our CI but it might be similar problem for our 
users who want to install the chart - they might also get the same kinds of 
error.
   
   I guess we should either make it more resilient to intermittent problems 
with bitnami charts or use another chart (or maybe even host the chart 
ourselves  somewhere within apache infrastructure. While the postgres chart is 
not really needed for most "production" users, it is still a dependency of our 
chart and it makes our chart depend on external and apparently flaky service.
   
   
   ### What you think should happen instead
   
   We should find (or host ourselves) more stable dependency or get rid of it. 
   
   ### How to reproduce
   
   Look at some recent CI builds and see that they often fail in K8S tests and 
more often than not the reason is missing postgresql chart.
   
   ### Operating System
   
   any
   
   ### Versions of Apache Airflow Providers
   
   not relevant
   
   ### Deployment
   
   Other
   
   ### Deployment details
   
   CI 
   
   ### Anything else
   
   Happy to make the change once we agree what's the best way :).
   
   ### 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