feat: add Gateway API HTTPRoute support with optional self-managed Gateway - #100
Merged
aaronzi merged 12 commits intoSep 17, 2026
Merged
Conversation
disco-stu
force-pushed
the
feature/gatewayapi-httproute
branch
from
September 9, 2026 16:24
afdfd45 to
c51822f
Compare
…f-managed Gateway
…elf-managed Gateway
disco-stu
force-pushed
the
feature/gatewayapi-httproute
branch
from
September 17, 2026 13:49
c51822f to
65c551a
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds opt-in Gateway API routing as an alternative to Ingress. Every BaSyx
service can now be exposed via a Gateway API
HTTPRouteinstead of (oralongside) an
Ingress, and the chart can optionally manage its ownGatewayresource for standalone/demo deployments that don't already haveone. Ingress remains the default routing mechanism; the feature is disabled
by default and fully backwards compatible.
Changes
<service>.httpRoute.{enabled,parentRefs,annotations,hosts}values anda
templates/<service>/httproute.yamlfor all 11 BaSyx servicescommon.httpRoute.parentRefshelper resolvingparentRefswith thisprecedence: service-local > chart-wide
gatewayApi.parentRefs>auto-derived reference to the chart-managed
Gateway> explicitfailwith an actionable error message
Gatewayresource(
gatewayApi.gateway.enabled, defaultfalse) with fixedhttp/httpslisteners, standard chart labels, and
classNamevalidation viarequired(...)cert-manager.io/issuer/cert-manager.io/cluster-issuerannotations on the
GatewayfromgatewayApi.gateway.issuer/clusterIssuer, deliberately decoupled from the existingingress.issuer/
ingress.clusterIssuervaluesvalues.schema.jsonwith the newgatewayApiobjectvalues/values.gatewayapi.example.yaml(bring-your-own Gateway) and
values/values.gatewayapi-managed.example.yaml(chart-managed Gateway)
(HTTPRoute)" section with value tables and the
parentRefsprecedencerules
3.12.0(appVersionunchanged at1.0.11, noBaSyx Go image change)
Validation
helm lint charts/basyx– 0 errorshelm unittest charts/basyx– 18 suites / 242 tests passing, includingnew
gateway_test.yamlandhttproute_test.yamlimplementation)