-
Notifications
You must be signed in to change notification settings - Fork 1
test: add proxy scale and concurrency coverage #70
Copy link
Copy link
Open
Labels
area: ciContinuous integration and GitHub automation.Continuous integration and GitHub automation.area: proxyProxy host configuration and request forwarding.Proxy host configuration and request forwarding.area: runtimeCaddy and privileged controller runtime behavior.Caddy and privileged controller runtime behavior.relatedRelated work that is not a confirmed duplicate.Related work that is not a confirmed duplicate.
Milestone
Description
Activity
Metadata
Metadata
Assignees
Labels
area: ciContinuous integration and GitHub automation.Continuous integration and GitHub automation.area: proxyProxy host configuration and request forwarding.Proxy host configuration and request forwarding.area: runtimeCaddy and privileged controller runtime behavior.Caddy and privileged controller runtime behavior.relatedRelated work that is not a confirmed duplicate.Related work that is not a confirmed duplicate.
Summary
Validate correctness, recovery, and bounded resource behavior with larger configurations and
concurrent management operations. This is not a benchmark contest and does not authorize invented
performance targets.
Workloads
Select and document realistic sizes from observed runtime cost, including:
The existing suggestion of roughly 100 Proxy Hosts is a starting scenario, not an unsupported
product guarantee.
Verify
workload envelope
behavior
Acceptance criteria
Priority and sequencing
P1. Build on the current revision/reconciliation and smoke-test foundations. Keep this
correctness-at-scale work distinct from the long-duration soak in #69. Results gate #75.