Add E2E for the MergeGateways feature

[arkodg]

Description:

Describe the issue.

Add an E2E in https://github.com/envoyproxy/gateway/tree/main/test/e2e for the MergeGateway features
Relates to #1938

[optional Relevant Links:]

Any extra documentation required to understand the issue.

[shawnh2]

it seems a little tricky to implement this e2e test case.

our e2e test env deploys eg with controller name:

gateway/test/config/gatewayclass.yaml

Line 6 in c85f0e4

controllerName: gateway.envoyproxy.io/gatewayclass-controller

if we have mergeGateways feature enabled, it's better to create a new gatewayclass, not reuse the exist one:

apiVersion: gateway.networking.k8s.io/v1
kind: GatewayClass
metadata:
  name: eg-merge-gateways
spec:
  controllerName: gateway.envoyproxy.io/merge-gateways-controller  # needs another controller name
  parametersRef:
    group: gateway.envoyproxy.io
    kind: EnvoyProxy
    name: custom-proxy-config
    namespace: envoy-gateway-system
---
apiVersion: gateway.envoyproxy.io/v1alpha1
kind: EnvoyProxy
metadata:
  name: custom-proxy-config
  namespace: envoy-gateway-system
spec:
  mergeGateways: true  # enable

but that requires to deploy eg one more time, it's not worthy!

[arkodg]

thanks for looking into this @shawnh2, maybe we can pause on this until #1231 is complete, which should make it easier to add and remove multiple gateway classes

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 30 days.

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 30 days.