Add Flower HTTPRoute support to Helm chart#69945
Conversation
Co-authored-by: Przemysław Mirowski <17602603+Miretpl@users.noreply.github.com>
Co-authored-by: Przemysław Mirowski <17602603+Miretpl@users.noreply.github.com>
|
Thanks for the reviews! If there's anything I can improve, please let me know 😄 |
Backport failed to create: chart/v1-2x-test. View the failure log Run detailsNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
You can attempt to backport this manually by running: cherry_picker 02a956f chart/v1-2x-testThis should apply the commit to the chart/v1-2x-test branch and leave the commit in conflict state marking After you have resolved the conflicts, you can continue the backport process by running: cherry_picker --continueIf you don't have cherry-picker installed, see the installation guide. |
|
@nailo2c could you do a manual backport of it to the 1.2x release line? |
|
Done, the backport PR is #70263 |
#70263) * Add Flower HTTPRoute support to Helm chart * Update chart/tests/helm_tests/other/test_httproute_flower.py * Clarify Flower HTTPRoute configuration guidance * Update chart/docs/production-guide.rst * Simplify HTTPRoute configuration guidance --------- (cherry picked from commit 02a956f) Co-authored-by: Przemysław Mirowski <17602603+Miretpl@users.noreply.github.com>
related: #61452
Summary
This adds Helm chart support for exposing Flower with Kubernetes Gateway API
HTTPRoute.flower.httpRoutevalues, schema, template, tests, and docs;ports.flowerUI;parentRefs, path settings, and fullrulesoverride;API Server HTTPRoute support was already added in #67675. This PR covers the remaining Flower scope for #61452.
Validation
E2E screenshot through the Gateway API path:

This was opened at
http://flower.localhost:8888/workerswhile port-forwarding the Envoy Gateway dataplane service, so the request path was:Was generative AI tooling used to co-author this PR?
Generated-by: [GPT-5] following the guidelines