potiuk commented on issue #10753: URL: https://github.com/apache/airflow/issues/10753#issuecomment-687661416
> I'll have to read the ASF thread (on mobile on the weekend) but why is releases of the helm chart, which is just a manifest ultimately, have any requirement on shipping the source code of one of the images? > > I can see the reason to publish source code for a release of the image. But the helm chart is just pointing at _already released and voted on_ images. Those voted releases would include the source already, no? > > Including sources for releases of a chat would never be used by 99.9% users, not even if the cases you highlighted. I just read it again @ashb and maybe this misunderstanding is the reason for a lot of discussion here. Helm Chart is NOT just metadata + image. Helm chart consist of: * metadata XML describing different version of the helm chart. This is basically index of different versions of the helm chart and where "tar.gz" content of each version can be found * the helm chart .tar.gz for each source is basically packaged sources from chart that allow the chart to "build" yaml files dynamically based on valuses specified. Those are mostly GO-templates for the yaml files+ yaml values + some extra sources needed (like config files etc.) - > this is the part that is in "charts" folder of Airflow repo and one that IMHO is the one that falls into "releaes" of ASF as those are clearly "sources" * those templates contains links to images used. And Here I believe we should give users an easy way to rebuild those images if they need to - using official binary images (such as python) + permissively licensed sources that the users know where to find and they are reasonably "protected" from suddenly disappearing. There was an important point in both - our and ASF discussion is that regardless if the chart files are kept in the same repo as the "main code" or separate, their release cadence should be different that that of the main "product". But they still MUST be released with signing, SVN etc. - as we are releasing some sources. The idea which I currently like most is that there is a separate place in Apache SVN that we can drop our "released" .tar.gz with Helm Chart and tooling to update the index to point to them + there should be a way for the users to build the images that are in the .tar.gz (ideally scripts in the same .tar.gz) if they need to. ---------------------------------------------------------------- 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]
