Looks like this might be a cleanup/setup issue with the new test:
2024-08-23T05:26:03.4745842Z === RUN TestGlooGatewayEdgeGateway/ClientTls/TestRouteSecureRequestToUpstream
2024-08-23T05:26:03.6627786Z secret/my-tls created
2024-08-23T05:26:03.8474524Z upstream.gloo.solo.io/nginx created
2024-08-23T05:26:04.0336110Z Error from server: error when creating "/home/runner/work/gloo/gloo/test/kubernetes/e2e/features/client_tls/testdata/vs-targeting-upstream.yaml": admission webhook "gloo.gloo-gateway-edge-test.svc" denied the request: resource incompatible with current Gloo snapshot: [Validating *v1.VirtualService failed: 1 error occurred:
2024-08-23T05:26:04.0338545Z * Validating *v1.VirtualService failed: validating *v1.VirtualService name:"vs-targeting-upstream" namespace:"gloo-gateway-edge-test": 1 error occurred:
2024-08-23T05:26:04.0339659Z * could not render proxy: 4 errors occurred:
2024-08-23T05:26:04.0340465Z * invalid resource gloo-gateway-edge-test.gateway-proxy
2024-08-23T05:26:04.0341619Z * domain conflict: the following domains are present in more than one of the virtual services associated with this gateway: [*]
2024-08-23T05:26:04.0343024Z * domain conflict: the [*] domain is present in other virtual services that belong to the same Gateway as this one: [gloo-gateway-edge-test.vs-targeting-upstream]
2024-08-23T05:26:04.0344509Z * domain conflict: the [*] domain is present in other virtual services that belong to the same Gateway as this one: [gloo-gateway-edge-test.vs-targeting-kube]
2024-08-23T05:26:04.0345224Z
2024-08-23T05:26:04.0345237Z
2024-08-23T05:26:04.0345242Z
2024-08-23T05:26:04.0345247Z
2024-08-23T05:26:04.0345251Z
2024-08-23T05:26:04.0345330Z ]
2024-08-23T05:26:04.0367251Z suite.go:98:
2024-08-23T05:26:04.0370355Z Error Trace: /home/runner/work/gloo/gloo/test/kubernetes/e2e/features/client_tls/suite.go:98
2024-08-23T05:26:04.0371670Z Error: Received unexpected error:
2024-08-23T05:26:04.0372939Z exit status 1
2024-08-23T05:26:04.0374425Z github.com/solo-io/gloo/pkg/utils/cmdutils.(*LocalCmd).Run
2024-08-23T05:26:04.0375924Z /home/runner/work/gloo/gloo/pkg/utils/cmdutils/local.go:91
2024-08-23T05:26:04.0377103Z github.com/solo-io/gloo/pkg/utils/kubeutils/kubectl.(*Cli).ApplyFileWithOutput
2024-08-23T05:26:04.0378809Z /home/runner/work/gloo/gloo/pkg/utils/kubeutils/kubectl/cli.go:142
2024-08-23T05:26:04.0380553Z github.com/solo-io/gloo/pkg/utils/kubeutils/kubectl.(*Cli).ApplyFile
2024-08-23T05:26:04.0383121Z /home/runner/work/gloo/gloo/pkg/utils/kubeutils/kubectl/cli.go:107
2024-08-23T05:26:04.0385424Z github.com/solo-io/gloo/test/kubernetes/e2e/features/client_tls.(*clientTlsTestingSuite).TestRouteSecureRequestToUpstream
2024-08-23T05:26:04.0387682Z /home/runner/work/gloo/gloo/test/kubernetes/e2e/features/client_tls/suite.go:97
2024-08-23T05:26:04.0388975Z reflect.Value.call
2024-08-23T05:26:04.0390555Z /opt/hostedtoolcache/go/1.22.4/x64/src/reflect/value.go:596
2024-08-23T05:26:04.0391587Z reflect.Value.Call
2024-08-23T05:26:04.0392590Z /opt/hostedtoolcache/go/1.22.4/x64/src/reflect/value.go:380
2024-08-23T05:26:04.0393824Z github.com/stretchr/testify/suite.Run.func1
2024-08-23T05:26:04.0395032Z /home/runner/go/pkg/mod/github.com/stretchr/testify@v1.8.4/suite/suite.go:197
2024-08-23T05:26:04.0395785Z testing.tRunner
2024-08-23T05:26:04.0396993Z /opt/hostedtoolcache/go/1.22.4/x64/src/testing/testing.go:1689
2024-08-23T05:26:04.0397667Z runtime.goexit
2024-08-23T05:26:04.0398544Z /opt/hostedtoolcache/go/1.22.4/x64/src/runtime/asm_amd64.s:1695
2024-08-23T05:26:04.0399453Z Test: TestGlooGatewayEdgeGateway/ClientTls/TestRouteSecureRequestToUpstream
2024-08-23T05:26:04.0400277Z Messages: can apply vs targeting upstream manifest file
2024-08-23T05:26:04.1520162Z want:
2024-08-23T05:26:04.1521181Z HttpResponse{StatusCode: 200, Body: &matchers.ContainSubstringMatcher{Substr:"Welcome to nginx!", Args:[]interface {}(nil)}, Headers: map[], Custom: <nil>}
2024-08-23T05:26:04.1522076Z stdout:
2024-08-23T05:26:04.1522332Z Gloo Gateway has invalid configuration.
Which tests failed?
Nightly kubernetes e2e tests on main: https://github.com/solo-io/gloo/actions/runs/10520175408/job/29148739547
Initial Investigation
Looks like this might be a cleanup/setup issue with the new test:
Additional Information
No response