Story (Required)

Kube burner tests now support waiting for statuses only for standard kubernetes resources like deployments, pods etc. Performance tests written for ArgoCD currently uses child object's status to indirectly determine if the application has reached Synced and Healthy status. This may not be right approach, instead kube burner should support waiting for status that are native for ArgoCD.

Background (Required)

Out of scope

None

Approach (Required)

• make kube burner to take a jqpath expression or JSON pointer object and the expected status till which the scripts have to wait and capture data.
• The changes have to done in the kube-burner project.
• Discuss the approach with the developers before finalizing.

Dependencies

Related issues upstream

https://github.com/argoproj/argo-cd/issues/6561

https://github.com/argoproj/argo-cd/issues/17236

Acceptance Criteria (Mandatory)

• Automated tests using kube-burner should be created. These tests should: 
  • Create a load testing setup for cluster scoped instance.
  • Create a large number of namespaces and Argo applications.
  • Deploy resources in these namespaces.
  • Capture and report metrics such as CPU, memory, threads, and IO usage.
  • Capture the time delay for application sync.
• The kube-burner configuration and the findings of the test should be in the gitops repository.

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