test(e2e): in MLBS + MZMS test, don't manually create MeshService (#1…

…1978) This is left over from when they weren't autogenerated on universal. Signed-off-by: Mike Beaumont <[email protected]>
kumahq · Nov 6, 2024 · 7d59c7b · 7d59c7b
1 parent c0883d4
commit 7d59c7b
Showing 1 changed file with 0 additions and 20 deletions.
diff --git a/test/e2e_env/multizone/localityawarelb/meshmultizoneservice.go b/test/e2e_env/multizone/localityawarelb/meshmultizoneservice.go
@@ -56,28 +56,8 @@ spec:
 			Install(democlient.Install(democlient.WithNamespace(namespace), democlient.WithMesh(meshName))).
 			SetupInGroup(multizone.KubeZone2, &group)
 
-		uniServiceYAML := `
-type: MeshService
-name: test-server
-mesh: mlb-mzms
-labels:
-  kuma.io/origin: zone
-  kuma.io/env: universal
-  k8s.kuma.io/namespace: mlb-mzms # add a label to aggregate kube and uni service
-  kuma.io/display-name: test-server # add a label to aggregate kube and uni service
-spec:
-  selector:
-    dataplaneTags:
-      kuma.io/service: test-server
-  ports:
-  - port: 80
-    targetPort: 80
-    appProtocol: http
-`
-
 		NewClusterSetup().
 			Install(TestServerUniversal("test-server", meshName, WithArgs([]string{"echo", "--instance", "uni-test-server"}))).
-			Install(YamlUniversal(uniServiceYAML)).
 			SetupInGroup(multizone.UniZone1, &group)
 		Expect(group.Wait()).To(Succeed())
 	})