Load test infra setup

[SimonTheLeg]

Summary

This PR adds a setup script to setup loadtesting on infra which has the required nodepools in place.

What Type of PR Is This?

/kind feature

Release Notes

NONE

[ntnn]

/assign

[ntnn]

I'll give it a try tomorrow, thanks for the work!

[ntnn]

I think we should explicitly list the expected node selector values, i.e. auxiliary, kcp-frontproxy, kcp-etcd, kcp-server

[SimonTheLeg]

I have now directly mentioned the kind example to look up to see all the different nodepools

[ntnn]

For reference I deployed this in infra, where it looks like its working and in kind where it breaks.

The kind setup:

1. Create kind with this config:

kind: Cluster
apiVersion: kind.x-k8s.io/v1alpha4
nodes:
  - role: control-plane
  - role: worker
    labels:
      role: "kcp-frontproxy"
  - role: worker
    labels:
      role: "kcp-etcd"
  - role: worker
    labels:
      role: "kcp-server"
  - role: worker
    labels:
      role: "auxiliary"

2. Create the kcp namespace
3. Create alias services:

apiVersion: v1
kind: Service
metadata:
  name: frontproxy
  namespace: kcp
spec:
  type: ExternalName
  externalName: frontproxy-front-proxy.kcp.svc.cluster.local
---
apiVersion: v1
kind: Service
metadata:
  name: root
  namespace: kcp
spec:
  type: ExternalName
  externalName: root-kcp.kcp.svc.cluster.local
---
apiVersion: v1
kind: Service
metadata:
  name: shard2
  namespace: kcp
spec:
  type: ExternalName
  externalName: shard2-shard-kcp.kcp.svc.cluster.local
---
apiVersion: v1
kind: Service
metadata:
  name: shard3
  namespace: kcp
spec:
  type: ExternalName
  externalName: shard3-shard-kcp.kcp.svc.cluster.local

4. Source these env values:

export NODEPOOL_SELECTOR="role"
export GATEWAY_BASE_URL="kcp.svc.cluster.local"
export GATEWAY_ANNOTATIONS="{'hello':'world'}"

5. Run setup.sh

Then e.g. front proxy fails with these messages:

E0309 09:35:22.187099       1 reflector.go:200] "Failed to watch" err="failed to list *v1alpha1.LogicalCluster: Get \"https://shard2.kcp.svc.cluster.local:6443/clusters/%2A/apis/core.kcp.io/v1alpha1/logicalclusters?limit=500&resourceVersion=0\": tls: failed to verify certificate: x509: certificate is valid for localhost, shard2-shard-kcp.kcp.svc.cluster.local, not shard2.kcp.svc.cluster.local" logger="UnhandledError" reflector="k8s.io/client-go@v0.0.0-20251113163256-f038ec6bf609/tools/cache/reflector.go:285" type="*v1alpha1.LogicalCluster"

I think adding the cert template should make this work in more setups

[SimonTheLeg]

I think all comments have been addressed ptal

[kcp-ci-bot]

LGTM label has been added.

Details

Git tree hash: cff99879aab7e7c86f735beeaf3135acc4e6a2e3

[ntnn]

/lgtm
/approve

[kcp-ci-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ntnn

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [ntnn]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment