# Feature request: Add support for multiple Gateways on HttpRoute (Kubernetes)

**URL:** <https://community.sonarsource.com/t/feature-request-add-support-for-multiple-gateways-on-httproute-kubernetes/188884>\
**Category:** Suggest new features\
**Tags:** kubernetes, helm\
**Created:** [September 25, 2026, 5:26am UTC](https://community.sonarsource.com/t/feature-request-add-support-for-multiple-gateways-on-httproute-kubernetes/188884 "2026-09-25T05:26:54Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![gian1200](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/gian1200/32/47277_2.png) [@gian1200](https://community.sonarsource.com/u/gian1200)\
**Post date:** [September 25, 2026, 5:26am UTC](https://community.sonarsource.com/t/feature-request-add-support-for-multiple-gateways-on-httproute-kubernetes/188884/1 "2026-09-25T05:26:54Z")

</div>

On [Integration of HTTPRoute Support in SonarQube Helm Chart](https://community.sonarsource.com/t/integration-of-httproute-support-in-sonarqube-helm-chart/112262), support for HttpRoute was added to Helm chart.

However, it currently supports reference to only 1 parentRef.

The [Gateway API spec](https://gateway-api.sigs.k8s.io/reference/api-types/httproute/) 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:**

```yaml
httproute:
  enabled: true
  gateway: my-gateway
  gatewayNamespace: my-gateway-namespace

```

**Proposed addition:**

```yaml
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.