On Integration of HTTPRoute Support in SonarQube Helm Chart, support for HttpRoute was added to Helm chart.
However, it currently supports reference to only 1 parentRef.
The Gateway API spec allows an HTTPRoute to declare multiple parentRefs, enabling a single route to be attached to more than one gateway simultaneously. This is a common pattern in enterprise environments where traffic is split between a public-facing and an internal gateway.
Current values schema:
httproute:
enabled: true
gateway: my-gateway
gatewayNamespace: my-gateway-namespace
Proposed addition:
httproute:
enabled: true
parentRefs:
- name: gateway-public
namespace: gateway-api
- name: gateway-internal
namespace: gateway-api
This would be backwards-compatible — the existing gateway/gatewayNamespace shorthand could remain for single-gateway setups, while parentRefs unlocks multi-gateway attachment for those who need it. Alternatively, gateway/gatewayNamespace could be deprecated in favour of parentRefs entirely, aligning the chart values more closely with the Gateway API spec.