-
Story
-
Resolution: Unresolved
-
Critical
-
None
-
False
-
None
-
False
-
SECFLOWOTL-72 - Baseline various Tekton Controller performance
-
-
Story (Required)
The customers wants information on Hub Resolver Performance.
Reference URL : https://tekton.dev/vault/pipelines-v0.50.x-lts/hub-resolver/
Background (Required)
The customer has all tasks in one namespace. All other namespaces use that.
Out of scope
<Defines what is not included in this story>
Approach (Required)
<Description of the general technical path on how to achieve the goal of the story. Include details like json schema, class definitions>
Dependencies
<Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>
Acceptance Criteria (Mandatory)
<Describe edge cases to consider when implementing the story and defining tests>
<Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story>
INVEST Checklist
Dependencies identified
Blockers noted and expected delivery timelines set
Design is implementable
Acceptance criteria agreed upon
Story estimated
Legend
Unknown
Verified
Unsatisfied
Done Checklist
- Code is completed, reviewed, documented and checked in
- Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
- Continuous Delivery pipeline(s) is able to proceed with new code included
- Customer facing documentation, API docs etc. are produced/updated, reviewed and published
- Acceptance criteria are met
- clones
-
SRVKP-4478 Explore Cluster Resolver performance
- Closed
- is cloned by
-
SRVKP-5865 Explore Git Resolver performance
- Closed
-
SRVKP-6097 Bundle Resolver Performance Testing
- Closed
1.
|
Test Hub-Resolver Performance | To Do | Siddardh R A | ||
2.
|
Create a scenario for hub-resolver | To Do | Unassigned |