Skip to content

docs: add virtwork vs kube-burner comparison#22

Merged
OchiengEd merged 1 commit into
mainfrom
kube-burner
Feb 23, 2026
Merged

docs: add virtwork vs kube-burner comparison#22
OchiengEd merged 1 commit into
mainfrom
kube-burner

Conversation

@mrhillsman

Copy link
Copy Markdown
Contributor

Add comprehensive technical comparison document explaining how virtwork and kube-burner solve adjacent but non-overlapping problems:

  • kube-burner measures platform handling of VMs (boot latency, migration)
  • virtwork generates workloads inside VMs for partner product validation

Update README with brief comparison section linking to full document.

@mrhillsman
mrhillsman requested a review from OchiengEd February 19, 2026 19:49
@exe-prow-github-app

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: mrhillsman

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

Details 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

@OchiengEd OchiengEd left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nitpicks but thorough otherwise.

Comment thread docs/virtwork-vs-kube-burner.md Outdated
Comment thread docs/virtwork-vs-kube-burner.md
Add comprehensive technical comparison document explaining how virtwork
and kube-burner solve adjacent but non-overlapping problems:
- kube-burner measures platform handling of VMs (boot latency, migration)
- virtwork generates workloads inside VMs for partner product validation

Update README with brief comparison section linking to full document.

Signed-off-by: Melvin Hillsman <mhillsma@redhat.com>
@OchiengEd
OchiengEd merged commit ae4838e into main Feb 23, 2026
1 check failed
@mrhillsman
mrhillsman deleted the kube-burner branch February 23, 2026 22:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants