potiuk commented on PR #32644: URL: https://github.com/apache/airflow/pull/32644#issuecomment-1645344070
We do not really release chart that often and certainly not to solve single problem like that. There is a quite an overhead for releasing software for us and we rather prefer to do it in semi-regular intervals, than "on demand" of individual users. But it is entirely not needed to be honest. The **right** way of doing it now is for you - until we relase the PR - is to extend the chart. Remember that helm chart is just a bunch of JINJA templates that produce K8S resources, no more than that. And you can easily extend or modify those resources on your own. One way to do it is to copy our chart, modify it and host it somewhere where you can install it from. S3 bucket, github raw URL, website, whatever - and you can install it from there. It's merely zip of the modified chart and metadata file next to it. And you do not even have to modify our chart or host it. This is pretty standard approach in Helm world that you extend a chart (a bit counter-intuitivel) by making the chart you want to extend a subchart of yours. This is for example what we do with the embedded Postgres and we could modify resources in it as needed. It is a subchart of Airflow, which means that all the resources it defines become part of the Airflow Chart. Same way you can have YourCompanyAirflowChart that has Airlfow 1.10 as a subchart and adds/overrides the resource you need (even hardcodes it as you probably already know what you miss). Then you should install your chart, and at the moment airflow releases 1.11 you will be able to switch back to "Pure Airflow". See: https://helm.sh/docs/chart_template_guide/subcharts_and_globals/. -- 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]
