feat(gateway-helm): support loadBalancerIP for LoadBalancer service type

[patsevanton]

What type of PR is this?
feat(gateway-helm)

What this PR does / why we need it:
This PR adds support for setting a static loadBalancerIP when the service type is configured as LoadBalancer. Currently, the Helm chart does not allow users to specify a pre-existing IP address for the LoadBalancer service, which can be required in certain environments (e.g., for IP whitelisting, DNS records, or network policies). With this change, users can define service.loadBalancerIP in their values file to assign a fixed IP to the Envoy Gateway service.

[patsevanton]

helm get manifest -n envoy-gateway-system eg | grep "kind: Service" -A 50

# Source: gateway-helm/templates/envoy-gateway-service.yaml
apiVersion: v1
kind: Service
metadata:
  name: envoy-gateway
  namespace: 'envoy-gateway-system'
  labels:
    control-plane: envoy-gateway
    helm.sh/chart: gateway-helm-v0.0.0-latest
    app.kubernetes.io/name: gateway-helm
    app.kubernetes.io/instance: eg
    app.kubernetes.io/version: "latest"
    app.kubernetes.io/managed-by: Helm
spec:
  type: ClusterIP
  selector:
    control-plane: envoy-gateway
    app.kubernetes.io/name: gateway-helm
    app.kubernetes.io/instance: eg
  ports:
  - name: grpc
    port: 18000
    targetPort: 18000
  - name: ratelimit
    port: 18001
    targetPort: 18001
  - name: wasm
    port: 18002
    targetPort: 18002
  - name: metrics
    port: 19001
    targetPort: 19001
  - name: webhook
    port: 9443
    targetPort: 9443

[patsevanton]

test with values:

service:
  # If set to PreferClose, the Envoy fleet will prioritize connecting to the Envoy Gateway pods that are topologically closest to them.
  trafficDistribution: ""
  annotations: {}
  type: "LoadBalancer"
  loadBalancerIP: "172.18.0.201"

helm get manifest -n envoy-gateway-system eg | grep "kind: Service" -A 50

# Source: gateway-helm/templates/envoy-gateway-service.yaml
apiVersion: v1
kind: Service
metadata:
  name: envoy-gateway
  namespace: 'envoy-gateway-system'
  labels:
    control-plane: envoy-gateway
    helm.sh/chart: gateway-helm-v0.0.0-latest
    app.kubernetes.io/name: gateway-helm
    app.kubernetes.io/instance: eg
    app.kubernetes.io/version: "latest"
    app.kubernetes.io/managed-by: Helm
spec:
  type: LoadBalancer
  loadBalancerIP: 172.18.0.201
  selector:
    control-plane: envoy-gateway
    app.kubernetes.io/name: gateway-helm
    app.kubernetes.io/instance: eg
  ports:
  - name: grpc
    port: 18000
    targetPort: 18000
  - name: ratelimit
    port: 18001
    targetPort: 18001
  - name: wasm
    port: 18002
    targetPort: 18002
  - name: metrics
    port: 19001
    targetPort: 19001
  - name: webhook
    port: 9443
    targetPort: 9443

[patsevanton]

Do I need to update the docs and changelog?

[jukie]

Running make gen-check locally will update docs and helm rendering.

Can you also include a test case update to https://github.com/envoyproxy/gateway/blob/main/test/helm/gateway-helm/service-customization.in.yaml?

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 72.33%. Comparing base (aa3ad43) to head (091cac2).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #7686      +/-   ##
==========================================
- Coverage   72.36%   72.33%   -0.03%     
==========================================
  Files         233      233              
  Lines       34343    34343              
==========================================
- Hits        24851    24843       -8     
- Misses       7712     7717       +5     
- Partials     1780     1783       +3     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[patsevanton]

i run command make gen-check and get error

go tool -modfile=/home/user/github/patsevanton/envoyproxy-gateway-fork/tools/go.mod buf generate
Failure: could not get module data for remote module "buf.build/cncf/xds": permission_denied: 403 Forbidden
make[1]: *** [tools/make/proto.mk:5: protos] Error 1
make[1]: Leaving directory '/home/user/github/patsevanton/envoyproxy-gateway-fork'
make: *** [Makefile:18: _run] Error 2

How debug

• Build and Test / ci-checks (pull_request)

and e2e tests?