# 015 — Mock cluster: platform-pool labels so the GitOps stack schedules locally

The m19 t003 sweep pinned the whole platform stack (kratos/hydra/openfga/openbao values, CNPG clusters, prometheus/loki, operator/api/dashboard) to `nodeSelector bex.co/pool: platform` + the `bex.co/platform` toleration — labels/taints no CAPD mock node carries. Result: any milestone that needs the GitOps stack on the mock (w4/m7 email flows, w4/m11 MFA, parts of w3/m5, w3/m6) gets a wall of Pending pods.

One fix unblocks all of them — pick one:

- `scripts/mock-cluster.sh` labels its worker nodes `bex.co/pool=platform` at create (no taint needed — selectors match, tolerations are no-ops on untainted nodes), or
- a nodeSelector-neutralizing sweep of `deploy/gitops/overlays/local/values/*.values.yaml` (the openbao local-values pattern already exists).

The label approach is one line and keeps local/prod values identical — prefer it. Sub-hour; blocks w4/m7 t002-t004 and w4/m11 t001 as written (their task files now reference this note).
