Hello
I am working on an Helm Chart for Kubernetes. You can find my proposal on kube-airflow#16. I plan to use this project to land it first, and then prepare a clean Helm chart here if you agree. I see plenty of pending Pull Request on this project, can I get some hints on how to help the integration ?
Don't hesitate to create a PR for a new chart. Make sure you follow best practices. If you use helm create with Helm 2.7+ you'll get an initial experience with current best practices applied.
https://github.com/kubernetes/charts/blob/master/CONTRIBUTING.md
https://github.com/kubernetes/helm/tree/master/docs/chart_best_practices
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
I still want to work on it. The change I needed has been integrated into airflow mainline, so I can now make the official PR to helm :)
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale
damned! Please so not close it yet, we are almost ready to publish :)
fwiw i am willing to be a beta tester of this helm chart as we are likely about to go all in on an airflow / kube stack.
Hi. You can have a look at this version: gh:gsemet/kube-airflow@helm_chart.
I am aligning the Helm chart in gh:gsemet/kube-airflow (master branch) with the WIP I am submitting here in #3959. Still some work to do.
I would be interested in testing as well as we are moving to airflow on K8.
Feel free to test and give me your feedback !
Same in my situation.
/remove-lifecycle rotten
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
For me the mergerequest is ready to merge. Need an approver
Are we going to merge this ?
Would really love to see this included.
@unguiculus ?
This issue is being automatically closed due to inactivity.
Hello. Can you please reopen it ? This pull request is pretty stable and used in production, and is ready to be merged. Please someone review it ?
@rolanddb ?
/remove-lifecycle stale
Not sure if this will work.
I am not in a position to merge this or reopen it. I do not maintain this repo.
I've personally put quite some effort in the chart and would like to see it merged. But I'm not sure what it will take to convince someone to merge it.
sadly i do not get anyone to review this pull request :(
Our company is interested in pursuing Airflow+kubernetes. Could someone describe to me how I would got about testing this branch? @gsemet
Hi. You can download (git clone) it and use with helm directly (as I do in my compagny)
@gsemet Would you be able to describe how to get helm to install airflow from the repo that was cloned. I attempted to run from the root of your cloned repo:
helm install --namespace "airflow" --name "airflow" incubator/airflow
and received the error:
Error: found in requirements.yaml, but missing in charts/ directory: postgresql, redis
Any suggestions?
it it not yet merged so it is not in incubator/airflow (not sure if it test file existant first).
You need to clone and then use helm install ... ./charts/incubator/airflow/ (maybe you need helm dependency build charts/incubator/airflow)
/remove-lifecycle stale
/remove-lifecycle rotten
+1
+1
+1
+1
Please vote on the MR, it is almost ready :) do not hesitate to test latest version and tell if you use it in production !
+1
Chart is now merged :) Thanks for all your help !
Most helpful comment
Hello. Can you please reopen it ? This pull request is pretty stable and used in production, and is ready to be merged. Please someone review it ?