-
Notifications
You must be signed in to change notification settings - Fork 725
[Initiative]: Scale and performance testing guidance #2233
Copy link
Copy link
Open
Labels
help wantedinit/not-startedInitiative has been accepted, but not started (in the backlog)Initiative has been accepted, but not started (in the backlog)kind/initiativeAn initiative or an item related to imitative processesAn initiative or an item related to imitative processesneeds-triageIndicates an issue or PR that has not been triaged yet (has a 'triage/foo' label applied)Indicates an issue or PR that has not been triaged yet (has a 'triage/foo' label applied)sub/project-reviewsTOC Project Review SubprojectTOC Project Review Subprojecttag/operational-resilienceTAG Operational ResilienceTAG Operational Resilience
Description
Activity
Metadata
Metadata
Assignees
Labels
help wantedinit/not-startedInitiative has been accepted, but not started (in the backlog)Initiative has been accepted, but not started (in the backlog)kind/initiativeAn initiative or an item related to imitative processesAn initiative or an item related to imitative processesneeds-triageIndicates an issue or PR that has not been triaged yet (has a 'triage/foo' label applied)Indicates an issue or PR that has not been triaged yet (has a 'triage/foo' label applied)sub/project-reviewsTOC Project Review SubprojectTOC Project Review Subprojecttag/operational-resilienceTAG Operational ResilienceTAG Operational Resilience
Type
Projects
- StatusShow more project fieldsNew
- StatusShow more project fieldsstatus/new
- StatusShow more project fieldsNo status
- StatusShow more project fieldsNo status
- StatusShow more project fieldsNo status
- StatusShow more project fieldsNo status
- StatusShow more project fieldsNo status
Name
Scale and performance testing guidance for CNCF projects
Short description
Define performance testing expectations by project type so DD reviewers and projects have clear benchmarks to target.
Responsible group
TAG Operational Resilience
Does the initiative belong to a subproject?
No
Subproject name
Primary contact
TBD — TAG Operational Resilience lead
Additional contacts
@angellk (TOC Chair, DD finding source)
Origin
DD finding (automated)
Initiative description
This initiative is a request from the TOC. During due diligence reviews, the TOC evaluates projects against incubation and graduation criteria. When the same finding appears across multiple projects, it signals an ecosystem-wide gap that would be better addressed through standardized guidance than repeated per-project recommendations.
This finding has appeared in 9 of 42 DD reports (21%) scanned over the last 5 years, including #2198 (HAMi), #2057 (Kyverno), #2038 (Microcks), #1165 (KubeEdge), and others. The most recent DD to surface this was Kyverno graduation DD (merged 2026-03-17).
DDs frequently recommend performance benchmark data, scale testing, or load testing documentation, but there is no standardized expectation for what constitutes adequate testing by project type. A database operator has different scale testing needs than a CLI tool or a controller. The Kyverno DD specifically called for "more proactive, high-scale performance testing internally" and the HAMi DD recommended "performance benchmark data covering expected overhead and isolation quality across common concurrent workload scenarios."
Scope: Define performance testing expectations segmented by project type (database/storage, controller/operator, CLI tool, library, specification). Include guidance on benchmark methodology, reproducibility, what to publish, and how DD reviewers should evaluate performance testing adequacy. Aligns with TAG Operational Resilience charter scope: "Performance" and "Testing."
Timeline: TBD
Deliverable(s) or exit criteria
Tracking document for meeting and progress
TBD