Hi. I am Gaetan Semet (gsemet), the main maintainer of the stable/airflow chart. I am pretty thrilled by this conversation, and would be glad to see the chart switch to an official image. While the chart is pretty stable and already used in production by many, I have limited time to maintain it, so I would be very happy to see it directly maintained by the community. Of course I will continue to help on it as much as possible.
Maybe we can start a dedicated discussion only for the chart, I have a few questions on how to proceeded: - who to put as new OWNERS of this chart - do you want to take full "ownership" of it, if so, how to proceed ? How the governance of the chart should be managed? - the current implementation uses, like said, the "puckle" image that is quite good and stable, and many users are quite happy with it. Switching to an official image will require to document the change quite exaustively, especially if some feature get lost in the process. - The current implementation use Celery executor, do you plan into switching completely to the Kubernetes Executor, or maintaining 2 configurations in the template files? Maybe a simple value for the executable would be enough, I don't know, I did not tried the kube executor actually. To my understanding, the kube executor starts/stops each task in a pod, which comes with major cost for each simple tasks. Would it be possible to keep the current Celery as default executor and let user switch to the kube executor? Just some other questions on AIP-26: - do you plan making alpine images as well? or minimal-ubuntu, to reduce the size as much as possible? - helm v3 is about to be released, and this may have a major impact on charts (especially they can be de-centralized). I do not know if this concern also the "stable" ones, but if so, it would make sense to host the chart aside of airflow's code, isn't it? So, tell you how could I help. Best Regards, Gaetan Semet > On Mon, Oct 14, 2019 at 8:42 AM Jarek Potiuk <[email protected]> > wrote: > > > Issue created! https://github.com/helm/charts/issues/17933 . Thanks > > Jonathan for feedback and bringing this up! > >
