gatewayApiResources.envoy.clientTrafficPolicySpec is not respected in GitLab 19.x / charts v10.x

Summary

The override gatewayApiResources.envoy.clientTrafficPolicySpec (docs) worked in GitLab 18.11.x but no longer has effect on GitLab 19.x (charts v10.x)

Steps to reproduce

1. Set a ClientTrafficPolicy via gatewayApiResources.envoy.clientTrafficPolicySpec in the helm chart.
2. Deploy the helm chart

Configuration used

https://gitlab.com/gitlab-com/gl-infra/gitlab-dedicated/instrumentor/-/blob/ec1c8e0c496dea7f61ab24325f3e24958c31b6ea/common/jsonnet/envoy.libsonnet#L61-90

Current behavior

The values do not take effect on the webservice, because the Helm Chart creates its own more specific ClientTrafficPolicy, which takes precedence.

For example:

 k -n default get clienttrafficpolicy
NAME                    AGE
gitlab-policy           82d
gitlab-webservice-ctp   7h

gitlab-webservice-ctp - is the more specific one with (targetRefs.sectionName: gitlab-web), so the general one gitlab-policy (no explicit targetRefs), containing our Dedicated-specific configuration, is ignored for Webservice.

Expected behavior

The override gatewayApiResources.envoy.clientTrafficPolicySpec should either take precedence or be merged with the chart defaults.

Versions

• Chart: (tagged version | branch | hash git rev-parse HEAD)
• Platform:
  • Cloud: (GKE | AKS | EKS | ?)
  • Self-hosted: (OpenShift | Minikube | Rancher RKE | ?)
• Kubernetes: (kubectl version)
  • Client:
  • Server:
• Helm: (helm version)
  • Client:
  • Server:

Relevant logs

n/a