Skip to content

Adding kube-burner version of batch workload#4058

Open
vishnuchalla wants to merge 1 commit into
kubernetes:masterfrom
vishnuchalla:kube-burner
Open

Adding kube-burner version of batch workload#4058
vishnuchalla wants to merge 1 commit into
kubernetes:masterfrom
vishnuchalla:kube-burner

Conversation

@vishnuchalla

@vishnuchalla vishnuchalla commented May 18, 2026 •
edited
Loading

Copy link
Copy Markdown

What type of PR is this?

This PR is for onboarding kube-burner tests as per the plan here, following up on the discussion on 03/12/2026 to start with a simple workload.

What this PR does / why we need it:

We need this PR so that we can use this configs to run kube-burner from the CI.

Special notes for your reviewer:

Initial PR to add kube-burner configs for the existing batch workload.

Testing

Tested an verified in local cluster

vchalla@vchalla-mac kube-burner % /Users/vchalla/myforks/kube-burner/bin/arm64/kube-burner init -c workloads/batch/config.yaml --user-data workloads/batch/overrides.yaml
time="2026-05-18 18:38:57" level=info msg="📁 Creating local indexer: indexer-0" file="metrics.go:82"
time="2026-05-18 18:38:57" level=info msg="🔥 Starting kube-burner (main@20be8b96410e9e35dd3eea9f7db779365f250beb) with UUID bba10b87-750f-485d-ab57-eaa046363333" file="job.go:86"
time="2026-05-18 18:38:58" level=info msg="Pre-load: images from job batch-jobs" file="pre_load.go:78"
time="2026-05-18 18:38:58" level=info msg="Pre-load: Creating DaemonSet using images [gcr.io/k8s-staging-perf-tests/sleep:v0.0.3] in namespace preload-kube-burner-80375" file="pre_load.go:293"
time="2026-05-18 18:38:58" level=info msg="Pre-load: Waiting for images to be pulled on 3 nodes (timeout 10m0s)" file="pre_load.go:96"
time="2026-05-18 18:39:04" level=info msg="Pre-load: All images pulled on 3 nodes" file="pre_load.go:134"
time="2026-05-18 18:39:04" level=info msg="Deleting 1 namespaces with label: kube-burner.io/job=preload" file="namespaces.go:65"
time="2026-05-18 18:39:11" level=info msg="Cleaning up previous runs for job: batch-jobs" file="job.go:102"
time="2026-05-18 18:39:11" level=info msg="Initializing measurements for job: batch-jobs" file="factory.go:104"
time="2026-05-18 18:39:11" level=info msg="Registered measurement: jobLatency" file="factory.go:139"
time="2026-05-18 18:39:12" level=info msg="Creating batch/v1, Resource=jobs latency watcher for batch-jobs using selector [kube-burner.io/runid=14754612-b910-4d87-8322-a2175a97f1c6]" file="base_measurement.go:81"
time="2026-05-18 18:39:12" level=info msg="Triggering job: batch-jobs" file="job.go:139"
time="2026-05-18 18:39:13" level=info msg="Waiting up to 4h0m0s for actions to be completed" file="create.go:270"
time="2026-05-18 18:39:49" level=info msg="Actions in namespace batch-workload-0 completed" file="waiters.go:77"
time="2026-05-18 18:39:49" level=info msg="Verifying created objects" file="utils.go:161"
time="2026-05-18 18:39:49" level=info msg="Job batch-jobs took 37s" file="job.go:234"
time="2026-05-18 18:39:49" level=info msg="Stopping measurement: jobLatency" file="factory.go:168"
time="2026-05-18 18:39:49" level=info msg="batch-jobs: StartTime 99th: 0 ms max: 0 ms avg: 0 ms" file="base_measurement.go:125"
time="2026-05-18 18:39:49" level=info msg="batch-jobs: Complete 99th: 35000 ms max: 35000 ms avg: 34700 ms" file="base_measurement.go:125"
time="2026-05-18 18:39:49" level=info msg="Indexing collected data from measurement: jobLatency" file="factory.go:180"
time="2026-05-18 18:39:49" level=info msg="Indexing metric jobLatencyMeasurement" file="base_measurement.go:158"
time="2026-05-18 18:39:49" level=info msg="File collected-metrics-bba10b87-750f-485d-ab57-eaa046363333/jobLatencyMeasurement-batch-jobs.json now contains 10 documents" file="base_measurement.go:167"
time="2026-05-18 18:39:49" level=info msg="Indexing metric jobLatencyQuantilesMeasurement" file="base_measurement.go:158"
time="2026-05-18 18:39:49" level=info msg="File collected-metrics-bba10b87-750f-485d-ab57-eaa046363333/jobLatencyQuantilesMeasurement-batch-jobs.json now contains 2 documents" file="base_measurement.go:167"
time="2026-05-18 18:39:49" level=info msg="Indexing job summaries" file="metadata.go:49"
time="2026-05-18 18:39:49" level=info msg="File collected-metrics-bba10b87-750f-485d-ab57-eaa046363333/jobSummary.json now contains 1 documents" file="metadata.go:66"
time="2026-05-18 18:39:49" level=info msg="Finished execution with UUID: bba10b87-750f-485d-ab57-eaa046363333" file="job.go:316"
time="2026-05-18 18:39:49" level=info msg="Waiting for garbage collection to finish" file="job.go:341"
time="2026-05-18 18:39:49" level=info msg="Deleting 1 namespaces with label: kube-burner.io/job=batch-jobs" file="namespaces.go:65"
time="2026-05-18 18:39:59" level=info msg="👋 Exiting kube-burner bba10b87-750f-485d-ab57-eaa046363333" file="kube-burner.go:89"

@vishnuchalla
Adding kube-burner version of batch workload
e600f8f 
Signed-off-by: Vishnu Challa <vchalla@redhat.com>
@linux-foundation-easycla

linux-foundation-easycla Bot commented May 18, 2026 •
edited
Loading

Copy link
Copy Markdown

CLA Signed
The committers listed above are authorized under a signed CLA.

  • ✅ login: vishnuchalla / name: Vishnu Challa (e600f8f)

@k8s-ci-robot k8s-ci-robot added the cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. label May 18, 2026
@k8s-ci-robot

k8s-ci-robot commented May 18, 2026

Copy link
Copy Markdown
Contributor

Welcome @vishnuchalla!

It looks like this is your first PR to kubernetes/perf-tests 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/perf-tests has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

@k8s-ci-robot k8s-ci-robot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label May 18, 2026
@k8s-ci-robot

k8s-ci-robot commented May 18, 2026

Copy link
Copy Markdown
Contributor

Hi @vishnuchalla. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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.

@k8s-ci-robot k8s-ci-robot requested a review from mengqiy May 18, 2026 21:42
@k8s-ci-robot

k8s-ci-robot commented May 18, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

@k8s-ci-robot k8s-ci-robot requested a review from wojtek-t May 18, 2026 21:42
@k8s-ci-robot k8s-ci-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. and removed cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. labels May 18, 2026
@serathius

serathius commented May 20, 2026

Copy link
Copy Markdown
Member

Was the plan presented to SIG-scalability and approved? I don't see any reviewers or comments.

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

Reviewers

@mengqiy mengqiy Awaiting requested review from mengqiy

@wojtek-t wojtek-t Awaiting requested review from wojtek-t

Assignees

No one assigned

Labels

cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@vishnuchalla @k8s-ci-robot @serathius