Uh oh!
There was an error while loading. Please reload this page.
Improve API server HTTPRoute config based on review feedback - #68552
Conversation
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
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 d2d9f4c 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. |
Miretpl
commented
Jul 1, 2026
@somaz94 could you do manual backport to |
* Move API server HTTPRoute under apiServer and add config guards * Require HTTPRoute parentRefs and document API server Ingress mutual exclusivity * Fail fast on empty HTTPRoute parentRefs via schema minItems * Apply pretty-format-json formatting to values.schema.json (cherry picked from commit d2d9f4c)
* Move API server HTTPRoute under apiServer and add config guards * Require HTTPRoute parentRefs and document API server Ingress mutual exclusivity * Fail fast on empty HTTPRoute parentRefs via schema minItems * Apply pretty-format-json formatting to values.schema.json (cherry picked from commit d2d9f4c) Co-authored-by: somaz <112675579+somaz94@users.noreply.github.com>
Follow-up to #67675 addressing post-merge review feedback from @Miretpl. The
original PR has not been released yet, so these refinements land before the
upcoming chart release as requested.
Changes:
httpRoute.apiServer.*toapiServer.httpRoute.*— it is an API-server setting, not a global one(values.yaml, values.schema.json, template, docs, tests).
apiServer.httpRoute.enabledis true but the Gateway API HTTPRoute CRD is not installed (via
.Capabilities.APIVersions.Has).ingress.apiServer.enabledandapiServer.httpRoute.enabledare set — HTTPRoute is an alternative to the API server Ingress.
spec.parentRefs/spec.rulesstructures, addasserts to the validation test, inline a single-use variable, and split the
parametrized creation test into separate cases (no inner
if).api_versionsparameter to therender_charthelper soCapabilities-gated templates render offline.
Validation:
helm templaterenders for enabled/disabled and fails as expected for both guardsrelated: #67675
Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Opus 4.8) following the guidelines