potiuk commented on PR #36991: URL: https://github.com/apache/airflow/pull/36991#issuecomment-1908412000
> @potiuk I've actually come around to this idea over time. You can sorta do it today with scaling those components to 0, but you end up with all that stuff in k8s anyways. Plus it also can help with the worker queues problem (#34219) - not super gracefully, mind you, but better than roll your own certainly, as you can just use multiple values files to keep it sane. > > I don't see this as being materially different than some of the other advanced stuff we expose to our users already. Fine for me then - if we are ready to support those cases :). I actually like it if we do it because this might help in some of the future descriptions of multi-tenant deployment. I initially thought that we do not want to make anything about Hel Chart with multitenancy, but actually now that you wrote it - it seems pretty plausible for anyone doing future multi-tenancy setup to do it by composing multiple charts. So yeah. I see how it can be useful if we want to support it. It would be good however maybe in this case to add a bit of documentation about that case - for example describe a few deployments (like the multiple queue case) to explain users what our intention is with those parameters. @kajanajustin - would you be open to add a short description of potential use cases for those parameters ? Maybe in "Production Guide" part of the docs: https://airflow.apache.org/docs/helm-chart/stable/production-guide.html ? -- 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. To unsubscribe, e-mail: commits-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
