potiuk commented on pull request #8777: URL: https://github.com/apache/airflow/pull/8777#issuecomment-639477121
I think we've already discussed it in the [mailing list](https://lists.apache.org/thread.html/r55b09d63a809428c20ca3317801cad5a86ac939478e0dbd8e93f0fee%40%3Cdev.airflow.apache.org%3E) and while I do not think we've officially voted on it, we agreed as community that we start from "basic" docker image for production (not puckel) for example (and helm chart donated officially by Astronomer). Astronomer's chart is indeed proven and works for a long time. It also has things like KEDA autoscaling etc. And I prefer stability in the first release than a lot of features. I agree it should use the official production image (which I will resume working on shortly - now after we started using the production image tests for our own Kubernetes tests) - just discussed that with @ashb and this is going to happen shortly and we are going to work together on bringing more features as needed. We know this is not going to be 1-1 transition for people who used the old chart, and we are fully aware of that - that was deliberate decision. Over time we might bring more features to the "former-Astronomer but soon community" chart. It's much more important that we have long term maintainability and support from the community than full set of features that were implemented in non-community managed chart. Having Astronomer team behind it - I am 100% sure maintainability is pretty much given and community can learn a thing or two from it. @ash @schnie @dimberman -> Maybe we should simply make an official vote on that? I think the discussion is done and we just need to cast a vote. I could not find an official vote for it but I think it is an important topic - important enough to have community official voting for it. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
