ClusterMesh scale: Phase 3 +4 — scale tiers + parallel CL2 fan-out + add all scenarios#1168
Draft
skosuri1 wants to merge 50 commits into
Draft
ClusterMesh scale: Phase 3 +4 — scale tiers + parallel CL2 fan-out + add all scenarios#1168skosuri1 wants to merge 50 commits into
skosuri1 wants to merge 50 commits into
Conversation
…tep, restore Endpoints (ip/v1)
…llback metric per scope
…oncurrent creates)
…idn't fix root cause); fix n5 condition syntax
…n10 in dev for n20 iteration
…N=20 mesh convergence
…s_v3 (DSv3 quota fits 1600 vCPU at n20)
… referenced it but variables.tf didn't declare)
…me _FakePopen attrs)
…flip prod skip_publish to false
…cross all clusters
…ments, harness knobs
…0 for smoke first
added 4 commits
May 11, 2026 18:17
…bined, sequential)
skosuri1
changed the title
added 16 commits
May 12, 2026 17:20
…ne n=2 smoke entry
…llapse, shifted args)
…ements + share-infra slot 3
…current=8, 720min timeout)
…e soft-fail + 240s timeout; n=2 smoke
…ibe + events) + pre-pull CL2 image to avoid ghcr.io parallel-pull rate-limit
… budget) replaces brittle 5min kubectl wait
…iserver-failure only
…tl jsonpath nested filter is broken; switch to shell-side filter
… + killer fix for HA + clustermesh-apiserver pod resource metrics; restore 4-scenario share-infra matrix
… pod-churn loop, peer sleep-observes; collect target-aware churn knobs; restore 5-scenario share-infra matrix
…current==mesh_size so every peer's Prometheus window overlaps target's churn
… scale + vmss delete-instances driven from execute.yml in parallel with CL2 observers
…fig parse + drop broken NewNodesAppearedInWindow PromQL + proactive failure debug dumps in node-churner.sh and execute.yml
…of agentpool label (label drift on k8s 1.34.7) + use kubeconfig-augmented JSON in scenario_failure_diag + tee kubectl stderr to debug log + debug_dump on every replace-phase abort path
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stacked on top of #1157 (
skosuri/clustermesh-scale). Do not merge until #1157 is merged; review/merge order matters.This PR continues the ClusterMesh scale-test scenario with Phase 3 work — moving from harness validation (2 small clusters) to real scale measurement across cluster-count tiers.
Phase 3 Deliverables
azure-5.tfvars,azure-10.tfvars,azure-20.tfvarsand corresponding pipeline matrix entries. Each tier: validate quota, validate peering count (N·(N-1) at separate-VNet mode — 380 at N=20), tune CL2 timeouts, document breaking points.utils.run_cl2_command(currently synchronous,modules/python/clusterloader2/utils.py:66-72) and confirming the AzDO agent has CPU/RAM headroom for N concurrent CL2 + Prometheus.Out of Scope (deferred to later phases / pre-merge of #1157)