It's not clear how the load tests can be run

Open Beginner friendly
#29 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Quiet
Tech stack
grafana, kubernetes, prometheus

Research direction

Start with the project README and the existing Locust load tests, then identify how a local Policy Server instance is started and where the k6 tests should be run. Update the README so a newcomer can run the k6 load tests against that local instance, and verify the documented steps from a clean setup.

Written by the indexing model from the issue text.

Description

area/scalability good first issue kind/tech-debt

The existing tests are written using locust, we want to migrate to k6. k6 will allow us to correlate the CPU/Memory usage with the load generated by the tests. k6 is an open source project from Grafana, hence it nicely integrates with the prometheus + grafana stack that Kubewarden already supports.

As a first step, we want the load tests to be ran against a local instance of Policy Server. We will work on running the load tests inside of a Kubernetes stack later on, since this is a bigger topic.

Acceptance criteria

  • The README of the project allows a newcomer to run the k6 load tests against a Policy Server instance he's running locally
Dominant language
Go Template
Stars
1
Forks
1
Avg merge
2d 9h
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from kubewarden/load-testing

All issues in kubewarden/load-testing

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.