Official helm chart released by the Airlfow Community

[potiuk]

Hello @thesuperzapper

The Airlfow community have finally released the "official" helm chart. Documentation here: http://airflow.apache.org/docs/helm-chart/stable/index.html

Release message/thread here: https://lists.apache.org/thread.html/r131d839158b8a7a92a7813183cae30d248be9e330ea2faaf9e654970%40%3Cdev.airflow.apache.org%3E

We've been discussing before about community providing support for the helm chart, and the community decided to continue with the helm chart donated by Astronomer. This is finally now fully available, released and will be maintained and supported by the community.

I wonder if you would like to continue having the separate chart and maintain it, or maybe you choose the path of deprecating it and helping the users to transition to the the "community managed" official chart. Having two charts in the

I think we are open to help with the transition if you choose that route and possibly even help with developing a transition documentation, how to switch etc. if you choose that route.

Let us know what you think.

[thesuperzapper]

For those following at home, I intend to maintain (and even add new features to) this chart as long as it's used. A little friendly competition often breeds innovation.

I have updated the README with a section highlighting that there are two charts, and outlining the approach that this "community" chart is taking.

However, let's make sure we refer to the charts by consistent names:

• "community" - is this chart
• "official" - is the chart found in the apache/airflow repo

[potiuk]

To be honest, I think "community" is quite a bit misleading name and it introduces a lot of confusion.

Everything Apache Airflow releases is a product of the "Apache Airflow Community". And at the Summit's talk Airflow Loves Kubernetes we are going to talk with @kaxil that the chart is supported by the Apache Airflow Community.

So I think we are going to refer to it as "Official Airflow Community Chart" from now on to be very precise this is not a product of some mysterious group - but the very same community that produces Apache Airflow.

[potiuk]

Hey @thesuperzapper - maybe we can propose another name for your chart that we can use, I really find it so confusing - several times I saw a question about the "community chart" in Slack and after asking for details (Which chart ?) I was pointed out to the https://airflow.apache.org/docs/helm-chart/stable/index.html . I really think people find it confusing because "Apache Airflow Community" is heavily used (and rightfully) to refer to the community build around Apache Airflow, which is built according to the Apache Way (Apache Software Foundation is the owner of Apache Airflow). And the "Community over code" is the ASF motto, so "community" as "distinctive" name is a very bad choice.

We could use 'Non-official" name but it is obviously negative (and there are other non-official charts like Bitnami one that is also often used). So maybe some other "name" that we can jointly refer to would be great? Let me think about some proposals.

[potiuk]

Just to explain - I also seek the right name here as we want to talk about it at the talk as an alternative and since it's going to be recorded and likely popular (my last year's Airflow Prod Docker Image talk from last year got whooping 7K views), I think we need to come up with a consistent naming that will be used by everyone.

I am thinking about some "positive" and "distinctive" names. I really do not want to leave people with an impression that there is something wrong with the "other" chart.

• It could be named by you @thesuperzapper - as you seem to be the author of almost all commits
• Simply "airflow-helm" chart (following the github repo name name) - might be a bit confusing
• "stable helm chart" - this is the name that people referred to for quite some time and still do (following the old name of the repo)
• "historical chart" - that might be slightly negative as it might mean as it is "outdated"
• "user-community chart" - similar to the "community" but with clear distinction from the "Airflow Community" which is more than users, they are also creators of Apache Airflow and various stakeholders

I like the last one most, because it's just a little modification of the current naming used by @thesuperzapper but one that brings clarity when it comes to distinction between the two, keeps the "community" part which is important for Matthew I think and is pretty informative.

WDYT?

[gsemet]

My humble opinion, as the original author of this chart: « user-community chart » is fine and not so far from what we have know.

[thesuperzapper]

I agree that user-community is fine.

When introducing it it's probably important to highlight that it it used to be the stable/airflow chart, so people understand where it came from (but that will probably become less understood/relevant as time passes).

[potiuk]

I agree that user-community is fine.

When introducing it it's probably important to highlight that it it used to be the stable/airflow chart, so people understand where it came from (but that will probably become less understood/relevant as time passes).

Cool. let's stick with that terminology then :). Surely - when we will talk about the Chart we want to tell shortly about the history and we want to make sure the credits are there for all the years when there was no Apache-Airflow-Community supported Helm Chart. I think many users might choose to stay with it and that's great if we can refer to history and explain the context, as it might sometimes (as in the discussion above) be not clear where the distinction originates from.