Skip to content

ci : test k6-operator install and load test execution in e2e workflow #1477

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

ci : test k6-operator install and load test execution in e2e workflow #1477

wants to merge 1 commit into from
+773 −0

Conversation

rohanKanojia
Copy link
Member

@rohanKanojia rohanKanojia commented Aug 1, 2025 •
edited
Loading

What does this PR do?

⚠️ Test PR to check how CI performs when we test minimal load test on it.

  • Execute load test after performing e2e tests
  • Add another Makefile target for load test execution with configuration options to override
    • max number of virtual users (VUs)
    • load Test duration
    • whether to create DevWorkspaces in separate namespaces or not
    • Timeout for DevWorkspace to get ready
    • Whether to create automount resources or not
  • Execute this target in e2e test script

What issues does this PR fix or reference?

Is it tested? How?

  • Login into OpenShift Cluster
  • Install DevWorkspace Operator
  • Run make test_load ARGS="--max-vus 500 --separate-namespaces false --test-duration-minutes 20"
    • To run test within pod run make test_load ARGS="--mode operator --max-vus 500 --separate-namespaces false --test-duration-minutes 20"

PR Checklist

  • E2E tests pass (when PR is ready, comment /test v8-devworkspace-operator-e2e, v8-che-happy-path to trigger)
    • v8-devworkspace-operator-e2e: DevWorkspace e2e test
    • v8-che-happy-path: Happy path for verification integration with Che

@openshift-ci OpenShift CI
Copy link

openshift-ci bot commented Aug 1, 2025

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@openshift-ci OpenShift CI
Copy link

openshift-ci bot commented Aug 1, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: rohanKanojia
Once this PR has been reviewed and has the lgtm label, please assign dkwon17 for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@rohanKanojia
Copy link
Member Author

/ok-to-test

rohanKanojia added a commit to rohankanojia-forks/devworkspace-operator that referenced this pull request Aug 1, 2025
@rohanKanojia
ci: compare CPU and memory usage between stable and PR DWO deployments (
33fc7d5 
devfile#1477)

- Deploy stable DevWorkspace Operator only on main branch
- Capture CPU and memory usage via `kubectl top` for both deployments
- Normalize and compare CPU/Memory metrics with configurable thresholds
- Fail CI if resource usage increases beyond acceptable limits
rohanKanojia added a commit to rohankanojia-forks/devworkspace-operator that referenced this pull request Aug 1, 2025
@rohanKanojia
ci: compare CPU and memory usage between stable and PR DWO deployments (
b1f7e60 
devfile#1477)

- Deploy stable DevWorkspace Operator only on main branch
- Capture CPU and memory usage via `kubectl top` for both deployments
- Normalize and compare CPU/Memory metrics with configurable thresholds
- Fail CI if resource usage increases beyond acceptable limits
@rohanKanojia rohanKanojia mentioned this pull request Aug 1, 2025
Draft
3 tasks
rohanKanojia added a commit to rohankanojia-forks/devworkspace-operator that referenced this pull request Aug 1, 2025
@rohanKanojia
ci: compare CPU and memory usage between stable and PR DWO deployments (
2024c54 
devfile#1477)

- Deploy stable DevWorkspace Operator only on main branch
- Capture CPU and memory usage via `kubectl top` for both deployments
- Normalize and compare CPU/Memory metrics with configurable thresholds
- Fail CI if resource usage increases beyond acceptable limits

Signed-off-by: Rohan Kumar <[email protected]>
@rohanKanojia
Copy link
Member Author

/ok-to-test

@rohanKanojia rohanKanojia changed the title ci : test k6 install and load test execution in e2e workflow ci : test k6-operator install and load test execution in e2e workflow Aug 13, 2025
@rohanKanojia
Copy link
Member Author

/ok-to-test

@rohanKanojia rohanKanojia force-pushed the pr/load-test-poc branch 2 times, most recently from 9cc315e to f65a955 Compare August 13, 2025 13:02
@rohanKanojia
Copy link
Member Author

/ok-to-test

@rohanKanojia
Copy link
Member Author

/ok-to-test

@rohanKanojia
Copy link
Member Author

/ok-to-test

@rohanKanojia
Copy link
Member Author

/ok-to-test

@rohanKanojia
Copy link
Member Author

/ok-to-test

1 similar comment
@rohanKanojia
Copy link
Member Author

/ok-to-test

@rohanKanojia
Copy link
Member Author

/ok-to-test

@rohanKanojia
ci : test k6 install and load test execution in e2e workflow
68abb57 
- Add another Makefile target for load test execution
- Execute this target in e2e test script

Signed-off-by: Rohan Kumar <[email protected]>
@rohanKanojia
Copy link
Member Author

/ok-to-test

@openshift-ci OpenShift CI
Copy link

openshift-ci bot commented Aug 14, 2025

@rohanKanojia: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/v14-devworkspace-operator-e2e 68abb57 link true /test v14-devworkspace-operator-e2e

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@dkwon17 dkwon17 Awaiting requested review from dkwon17 dkwon17 will be requested when the pull request is marked ready for review dkwon17 is a code owner

@ibuziuk ibuziuk Awaiting requested review from ibuziuk ibuziuk will be requested when the pull request is marked ready for review ibuziuk is a code owner

@akurinnoy akurinnoy Awaiting requested review from akurinnoy akurinnoy will be requested when the pull request is marked ready for review akurinnoy is a code owner

At least 1 approving review is required to merge this pull request.

Assignees
No one assigned
Labels
do-not-merge/work-in-progress ok-to-test
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@rohanKanojia