install-ate.sh: kind component deploys use GKE OTel endpoint #702

Problem

On kind, --deploy-atenet and --deploy-ate-apiserver apply the base manifests instead of the kind Kustomize overlay. The base manifests set:

OTEL_EXPORTER_OTLP_ENDPOINT=http://opentelemetry-collector.gke-managed-otel.svc.cluster.local:4317

That collector exists on GKE, not in the kind stack, so the redeployed component cannot export OTLP telemetry. --deploy-atelet is not affected by this endpoint bug because it already renders a component-specific kind overlay.

Reproduction

hack/install-ate-kind.sh --deploy-ate-system
hack/install-ate-kind.sh --deploy-atenet
kubectl get deployment/atenet-router -n ate-system \
  -o jsonpath='{.spec.template.spec.containers[?(@.name=="atenet-router")].env[?(@.name=="OTEL_EXPORTER_OTLP_ENDPOINT")].value}'

The command returns the gke-managed-otel endpoint. The kind deployment should use:

http://opentelemetry-collector.otel-system.svc:4317

--deploy-ate-apiserver has the same problem.

Fix

Add component-specific kind overlays for atenet and ate-api-server, and use them when ATE_INSTALL_KIND=true. Keep the existing base-manifest path for GKE.

Acceptance criteria

• Both partial kind deploys render the otel-system endpoint.
• The ate-api-server partial overlay retains the kind metric interval and timeout settings.
• Non-kind deploy behavior is unchanged.
• The metrics E2E observes router telemetry after the SDK export interval.