potiuk commented on issue #10523: URL: https://github.com/apache/airflow/issues/10523#issuecomment-684546842
Let's talk about constructive approach then @thesuperzapper :). I'd love to know how we can get the "airlfow" chart to a usable state by a normal person. The whole discussion is all about that I believe. We know that it misses a little to be completely ready for production, so I propose we all focus on making it happens as soon as possible: 1) Could you please point out what kind of documentation you think is missing in https://github.com/apache/airflow/blob/master/chart/README.md ? I am happy to help in improving the docs as a good community member, but I think your experience from the "stable" chart might be invaluable to point out what can be improved. Ideally a Github Issue would be great - then we can even ask our community members to improve it as we have an [ongoing effort to improve documentation](https://github.com/apache/airflow/issues?q=is%3Aissue+is%3Aopen+label%3Aarea%3Adocs) and our community members are super-helpful in improving it. 2) Could you please list the issues that are missing in the new chart and you think they are really useful and used in the 'stable chart'. I will be happy to bring some of those in (or help to decide that we don't migrate it). Ideally one issue per feature. Even if I am on vacations, I am happy to help in my free time to organize a bit the effort around it, label the issues and make some of them marked as "good-first-issue" so that our community members can possibly even help in implementing it. But we need to have those issues created to be able to act on them. I think our common goal should be to make it as easy for the current 'stable' helm users to migrate to the new chart (that was the community decision rather than adopting the original help) and your help there might be super valuable. Just a personal comment, I understand, and sorry for that if you feel a bit bitter that we have not adopted the chart of yours directly. I am afraid this was the community decision and voting on it passed a long time ago, and we made significant investments in making the current "airflow" helm chart part of the test/integration pipelines first - to make sure that we can support and maintain it in the long term. We often - as a community - make decisions that have no immediate impact but are made with the "long-term maintenance" point of view. The current chart will soon become a central point of "Kubernetes tests" - we are going to implement many more of those, we already unit-test part of it automatically and we have a commitment to make it rock solid and tested for 2.0 release (and also support latest 1.10.12). I think the best course of action is now to work together on making it happen. I think your help in identifying what can be improved in the "airflow/chart" might be invaluable. ---------------------------------------------------------------- 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]
