projects/gateway2/setup: Remove Settings CR from setup.yaml

This removes the Settings CR from the setup.yaml bootstrap
configuration in the envtests. The kgateway chart does not
carry this CR over to it's crds/ directory or have the RBAC
permissions to watch, list, etc. the resource.

Previously, we removed the legacy Settings logic in the gateway2
control plane in #10458, so this resource is no longer necessary
in the setup.yaml and envtest fails trying to deploy it with the
new chart.

Signed-off-by: timflannagan <[email protected]>

projects/gateway2/setup/testdata/setupyaml/setup.yaml

@@ -16,47 +16,3 @@ metadata:
   name: kgateway
 spec:
   kube: {}
----
-apiVersion: gloo.solo.io/v1
-kind: Settings
-metadata:
-  name: default
-spec:
-  discovery:
-    fdsMode: WHITELIST
-  discoveryNamespace: gloo-system
-  gateway:
-    enableGatewayController: true
-    isolateVirtualHostsBySslConfig: true
-    readGatewaysFromAllNamespaces: false
-    validation:
-      allowWarnings: true
-      alwaysAccept: false
-      disableTransformationValidation: false
-      fullEnvoyValidation: false
-      proxyValidationServerAddr: gloo:9988
-      serverEnabled: true
-      validationServerGrpcMaxSizeBytes: 104857600
-      warnMissingTlsSecret: true
-      warnRouteShortCircuiting: true
-  gloo:
-    disableKubernetesDestinations: false
-    disableProxyGarbageCollection: false
-    enableRestEds: false
-    invalidConfigPolicy:
-      invalidRouteResponseBody: Gloo Gateway has invalid configuration. Administrators
-        should run `glooctl check` to find and fix config errors.
-      invalidRouteResponseCode: 404
-      replaceInvalidRoutes: true
-    istioOptions:
-      appendXForwardedHost: true
-      enableAutoMtls: true
-      enableIntegration: true
-    proxyDebugBindAddr: 0.0.0.0:9966
-    regexMaxProgramSize: 1024
-    restXdsBindAddr: 0.0.0.0:9976
-    xdsBindAddr: 0.0.0.0:9977
-  kubernetesArtifactSource: {}
-  kubernetesConfigSource: {}
-  kubernetesSecretSource: {}
-  refreshRate: 60s