Skip to content

[WIP] OCPKUEUE-613: Install helm in Kueue DRA e2e test step for dra-example-driver validation#77988

Open
anahas-redhat wants to merge 1 commit intoopenshift:mainfrom
anahas-redhat:kueue-helm
Open

[WIP] OCPKUEUE-613: Install helm in Kueue DRA e2e test step for dra-example-driver validation#77988
anahas-redhat wants to merge 1 commit intoopenshift:mainfrom
anahas-redhat:kueue-helm

Conversation

@anahas-redhat
Copy link
Copy Markdown
Contributor

@anahas-redhat anahas-redhat commented Apr 17, 2026

The DRA e2e test suite includes a vendor-neutral validation test that deploys dra-example-driver via Helm, but the CI image does not include the helm binary.
This change installs helm v3.17.3 in the e2e-kueue-dra step before running the tests.

Testing against multiple drivers is a requirement of OCPKUEUE-574, ensuring Kueue's DRA support remains vendor-agnostic.

As a next step, the automated test will be added to the Kueue DRA test suite.

Summary by CodeRabbit

Release Notes

  • Chores
    • DRA e2e test environment now installs a pinned Helm v3.17.3 binary during test execution.
    • The Helm binary is downloaded and checksum-verified before tests run to ensure a consistent, reproducible test environment.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Apr 17, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

openshift-ci-robot commented Apr 17, 2026

@anahas-redhat: This pull request references OCPKUEUE-613 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.0.0" version, but no target version was set.

Details

In response to this:

The DRA e2e test suite includes a vendor-neutral validation test that deploys dra-example-driver via Helm, but the CI image does not include the helm binary.
This change installs helm v3.17.3 in the e2e-kueue-dra step before running the tests.

Testing against multiple drivers is a requirement of OCPKUEUE-574, ensuring Kueue's DRA support remains vendor-agnostic.

As a next step, the automated test will be added to the Kueue DRA test suite.

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 17, 2026
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Apr 17, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 3b99c004-2591-422e-ae1c-ad14917e518f

📥 Commits

Reviewing files that changed from the base of the PR and between 21b2c14 and 55b6849.

📒 Files selected for processing (1)
  • ci-operator/step-registry/kueue-operator/test/e2e/dra/kueue-operator-test-e2e-dra-chain.yaml
✅ Files skipped from review due to trivial changes (1)
  • ci-operator/step-registry/kueue-operator/test/e2e/dra/kueue-operator-test-e2e-dra-chain.yaml

Walkthrough

The DRA e2e test chain now installs Helm v3.17.3 at runtime by downloading the Linux tarball, verifying its SHA256, extracting linux-amd64/helm, and placing it at /usr/local/bin/helm before running the e2e test target.

Changes

Cohort / File(s) Summary
Helm Installation in CI Chain
ci-operator/step-registry/kueue-operator/test/e2e/dra/kueue-operator-test-e2e-dra-chain.yaml
Adds steps to download helm v3.17.3 from get.helm.sh, verify the .sha256sum, extract linux-amd64/helm, and install it to /usr/local/bin/helm prior to invoking make e2e-ci-test-dra.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes


Important

Pre-merge checks failed

Please resolve all errors before merging. Addressing warnings is optional.

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Stable And Deterministic Test Names ❓ Inconclusive Unable to access repository files or git information to analyze PR changes for Ginkgo test modifications. Provide access to the repository or share the git diff output to complete the analysis of modified files and test names.
✅ Passed checks (9 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly describes the main change: installing Helm in the Kueue DRA e2e test step, which matches the file modification that adds Helm v3.17.3 installation commands.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Test Structure And Quality ✅ Passed The check reviews Ginkgo test code quality in Go test files, but the PR only modifies a YAML CI configuration file without any Go test code changes, making the check not applicable.
Microshift Test Compatibility ✅ Passed PR modifies only a CI chain YAML file to install Helm v3.17.3, not adding new Ginkgo e2e test code.
Single Node Openshift (Sno) Test Compatibility ✅ Passed This PR does not introduce new Ginkgo e2e tests. Changes are limited to CI chain configuration installing Helm v3.17.3 as a prerequisite for existing tests.
Topology-Aware Scheduling Compatibility ✅ Passed The pull request modifies only CI test step configuration to install a Helm binary during test execution, introducing no scheduling constraints or topology-dependent assumptions.
Ote Binary Stdout Contract ✅ Passed Pull request only modifies YAML CI configuration file by adding Helm binary installation commands. No Go code, test binaries, or process-level code is modified, so the OTE Binary Stdout Contract check is not applicable.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed This PR modifies only CI step configuration (YAML) to install Helm v3.17.3, not adding new Ginkgo e2e tests, so the check does not apply.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands and usage tips.

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Apr 17, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: anahas-redhat
Once this PR has been reviewed and has the lgtm label, please assign cpmeadors 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

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

openshift-ci-robot commented Apr 17, 2026

@anahas-redhat: This pull request references OCPKUEUE-613 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.0.0" version, but no target version was set.

Details

In response to this:

The DRA e2e test suite includes a vendor-neutral validation test that deploys dra-example-driver via Helm, but the CI image does not include the helm binary.
This change installs helm v3.17.3 in the e2e-kueue-dra step before running the tests.

Testing against multiple drivers is a requirement of OCPKUEUE-574, ensuring Kueue's DRA support remains vendor-agnostic.

As a next step, the automated test will be added to the Kueue DRA test suite.

Summary by CodeRabbit

Release Notes

  • Chores
  • Updated DRA e2e test environment to install Helm v3.17.3 during test execution.

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot requested review from kannon92 and rphillips April 17, 2026 19:02
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In
`@ci-operator/step-registry/kueue-operator/test/e2e/dra/kueue-operator-test-e2e-dra-chain.yaml`:
- Line 39: The current single-line install (curl ... | tar xz -C /tmp && mv
/tmp/linux-amd64/helm /usr/local/bin/helm) lacks integrity checks; change it to
download the helm-v3.17.3-linux-amd64.tar.gz to a temp file, obtain a trusted
SHA256 (either by fetching the matching .sha256 from the Helm release or
embedding the expected hash), verify the tarball with sha256sum (or equivalent)
and abort on mismatch, and only then extract and mv the validated archive to
/usr/local/bin/helm so that extraction never runs on an unverified artifact.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: b7737d6d-dcda-4518-ab5d-6cb16dc0b6e2

📥 Commits

Reviewing files that changed from the base of the PR and between e1ef0b9 and 21b2c14.

📒 Files selected for processing (1)
  • ci-operator/step-registry/kueue-operator/test/e2e/dra/kueue-operator-test-e2e-dra-chain.yaml

…r validation

The DRA e2e test suite includes a vendor-neutral validation test (S5)
that deploys dra-example-driver via Helm, but the CI image does not
include the helm binary. Install helm v3.17.3 in the e2e-kueue-dra
step before running the tests.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

openshift-ci-robot commented Apr 17, 2026

@anahas-redhat: This pull request references OCPKUEUE-613 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.0.0" version, but no target version was set.

Details

In response to this:

The DRA e2e test suite includes a vendor-neutral validation test that deploys dra-example-driver via Helm, but the CI image does not include the helm binary.
This change installs helm v3.17.3 in the e2e-kueue-dra step before running the tests.

Testing against multiple drivers is a requirement of OCPKUEUE-574, ensuring Kueue's DRA support remains vendor-agnostic.

As a next step, the automated test will be added to the Kueue DRA test suite.

Summary by CodeRabbit

Release Notes

  • Chores
  • DRA e2e test environment now installs a pinned Helm v3.17.3 binary during test execution.
  • The Helm binary is downloaded and checksum-verified before tests run to ensure a consistent, reproducible test environment.

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-merge-bot
Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@anahas-redhat: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name Repo Type Reason
periodic-ci-openshift-kueue-operator-main-test-e2e-dra-gpu-4-21 N/A periodic Registry content changed
Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

@anahas-redhat
Copy link
Copy Markdown
Contributor Author

/pj-rehearse periodic-ci-openshift-kueue-operator-main-test-e2e-dra-gpu-4-21

@openshift-merge-bot
Copy link
Copy Markdown
Contributor

@anahas-redhat: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Apr 17, 2026

@anahas-redhat: 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/rehearse/periodic-ci-openshift-kueue-operator-main-test-e2e-dra-gpu-4-21 55b6849 link unknown /pj-rehearse periodic-ci-openshift-kueue-operator-main-test-e2e-dra-gpu-4-21

Full PR test history. Your PR dashboard.

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. 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

Labels

do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants