Skip to content

OCPBUGS-85344: enable karpenter tests for hypershift e2e-aws on 4.22#79051

Open
enxebre wants to merge 1 commit intoopenshift:mainfrom
enxebre:hypershift-karpenter-4-22
Open

OCPBUGS-85344: enable karpenter tests for hypershift e2e-aws on 4.22#79051
enxebre wants to merge 1 commit intoopenshift:mainfrom
enxebre:hypershift-karpenter-4-22

Conversation

@enxebre
Copy link
Copy Markdown
Member

@enxebre enxebre commented May 8, 2026

Summary

  • Add RUN_KARPENTER_TESTS=true env var to the e2e-aws test in the hypershift release-4.22 CI config
  • This enables karpenter e2e tests to run against 4.22 hosted clusters when the HyperShift operator is built from main
  • The karpenter API (karpenter.hypershift.openshift.io/v1) only exists on main, but can be tested against 4.22 clusters with this gate

Context

Depends on openshift/hypershift#8466 which adds the RUN_KARPENTER_TESTS env var check to lower the version gate from 4.23 to 4.22 for karpenter tests.

Fixes https://issues.redhat.com/browse/OCPBUGS-85344

Test plan

  • Verify CI presubmit checks pass
  • Confirm e2e-aws job picks up RUN_KARPENTER_TESTS=true and runs karpenter tests against 4.22 clusters

🤖 Generated with Claude Code

Enables running Karpenter e2e tests for HyperShift 4.22 in the OpenShift CI configuration. The PR updates HyperShift CI to set RUN_KARPENTER_TESTS: "true" for the e2e-aws-4-22 job (ci-operator/config/openshift/hypershift/openshift-hypershift-main.yaml), and adds the RUN_KARPENTER_TESTS environment variable (default "false") in the hypershift AWS nested e2e step definition (ci-operator/step-registry/hypershift/aws/run-e2e/nested/hypershift-aws-run-e2e-nested-ref.yaml). Practically, this lets the OpenShift CI run Karpenter e2e tests against 4.22 hosted clusters when the HyperShift operator is built from main — relying on the dependent HyperShift change that implements the gate and lowers the version requirement from 4.23 to 4.22. Fixes OCPBUGS-85344.

Test plan: ensure presubmit CI passes and verify the e2e-aws job picks up RUN_KARPENTER_TESTS=true and executes Karpenter tests against 4.22 clusters.

@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels May 8, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@enxebre: This pull request references Jira Issue OCPBUGS-85344, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (5.0.0) matches configured target version for branch (5.0.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Summary

  • Add RUN_KARPENTER_TESTS=true env var to the e2e-aws test in the hypershift release-4.22 CI config
  • This enables karpenter e2e tests to run against 4.22 hosted clusters when the HyperShift operator is built from main
  • The karpenter API (karpenter.hypershift.openshift.io/v1) only exists on main, but can be tested against 4.22 clusters with this gate

Context

Depends on openshift/hypershift#8466 which adds the RUN_KARPENTER_TESTS env var check to lower the version gate from 4.23 to 4.22 for karpenter tests.

Fixes https://issues.redhat.com/browse/OCPBUGS-85344

Test plan

  • Verify CI presubmit checks pass
  • Confirm e2e-aws job picks up RUN_KARPENTER_TESTS=true and runs karpenter tests against 4.22 clusters

🤖 Generated with Claude Code

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.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 8, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 7ff8b9f3-eb34-433e-b1f7-3c237c1956e9

📥 Commits

Reviewing files that changed from the base of the PR and between 0721668 and 116ecda.

📒 Files selected for processing (2)
  • ci-operator/config/openshift/hypershift/openshift-hypershift-main.yaml
  • ci-operator/step-registry/hypershift/aws/run-e2e/nested/hypershift-aws-run-e2e-nested-ref.yaml
✅ Files skipped from review due to trivial changes (1)
  • ci-operator/step-registry/hypershift/aws/run-e2e/nested/hypershift-aws-run-e2e-nested-ref.yaml
🚧 Files skipped from review as they are similar to previous changes (1)
  • ci-operator/config/openshift/hypershift/openshift-hypershift-main.yaml

Walkthrough

Adds a new environment variable RUN_KARPENTER_TESTS with a default of "false" to the hypershift AWS nested E2E step-ref and sets RUN_KARPENTER_TESTS: "true" in the e2e-aws-4-22 job in the OpenShift Hypershift CI operator config.

Changes

Karpenter Test Flag Propagation

Layer / File(s) Summary
Parameter / Default
ci-operator/step-registry/hypershift/aws/run-e2e/nested/hypershift-aws-run-e2e-nested-ref.yaml
Adds RUN_KARPENTER_TESTS to the step-ref env list with default value "false".
Job Override / Binding
ci-operator/config/openshift/hypershift/openshift-hypershift-main.yaml
Sets RUN_KARPENTER_TESTS: "true" in the e2e-aws-4-22 job's env block, overriding the default for that job.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

🚥 Pre-merge checks | ✅ 12
✅ Passed checks (12 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and specifically describes the main change: enabling karpenter tests for hypershift e2e-aws on 4.22, which aligns with the changeset modifications.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names ✅ Passed This PR modifies CI/CD YAML configuration files, not Ginkgo test code. No Ginkgo test definitions are introduced, so the check is not applicable.
Test Structure And Quality ✅ Passed PR contains only CI/CD configuration YAML files, not Ginkgo test code. The custom check for test structure is not applicable to configuration files.
Microshift Test Compatibility ✅ Passed No new Ginkgo e2e tests added. PR only modifies CI YAML configuration files to enable existing tests via environment variables (RUN_KARPENTER_TESTS). Check is not applicable.
Single Node Openshift (Sno) Test Compatibility ✅ Passed PR modifies only CI config YAML files, not test code. Enables existing karpenter e2e tests via environment variable. Custom check applies only to new Ginkgo tests, which is not applicable here.
Topology-Aware Scheduling Compatibility ✅ Passed This PR modifies only CI configuration files (test parameters), not deployment manifests, operator code, or controllers. The custom check does not apply to CI configuration changes.
Ote Binary Stdout Contract ✅ Passed PR only modifies CI configuration YAML files. OTE Binary Stdout Contract check applies to Go source code, not CI configuration. Not applicable.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed Not applicable. PR modifies CI configuration files only to enable existing tests via environment variables. No new Ginkgo test code is added, so the IPv6/disconnected check does not apply.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ 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 openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 8, 2026
@openshift-ci openshift-ci Bot requested review from clebs and sjenning May 8, 2026 16:02
@enxebre enxebre force-pushed the hypershift-karpenter-4-22 branch from 98b452e to 0721668 Compare May 8, 2026 16:03
@csrwng
Copy link
Copy Markdown
Contributor

csrwng commented May 8, 2026

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label May 8, 2026
Set RUN_KARPENTER_TESTS=true in the e2e-aws-4-22 test env in the
main config. This allows the karpenter e2e tests to run against
4.22 hosted clusters when the operator is built from main.

Depends on: openshift/hypershift#8466

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@enxebre enxebre force-pushed the hypershift-karpenter-4-22 branch from 0721668 to 116ecda Compare May 8, 2026 16:09
@openshift-ci openshift-ci Bot removed the lgtm Indicates that a PR is ready to be merged. label May 8, 2026
@openshift-merge-bot
Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@enxebre: 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
pull-ci-openshift-aws-karpenter-provider-aws-main-e2e-hypershift openshift/aws-karpenter-provider-aws presubmit Registry content changed
pull-ci-openshift-aws-karpenter-provider-aws-release-5.1-e2e-hypershift openshift/aws-karpenter-provider-aws presubmit Registry content changed
pull-ci-openshift-aws-karpenter-provider-aws-release-5.0-e2e-hypershift openshift/aws-karpenter-provider-aws presubmit Registry content changed
pull-ci-openshift-aws-karpenter-provider-aws-release-4.23-e2e-hypershift openshift/aws-karpenter-provider-aws presubmit Registry content changed
pull-ci-openshift-aws-karpenter-provider-aws-release-4.22-e2e-hypershift openshift/aws-karpenter-provider-aws presubmit Registry content changed
pull-ci-openshift-aws-karpenter-provider-aws-release-4.21-e2e-hypershift openshift/aws-karpenter-provider-aws presubmit Registry content changed
pull-ci-openshift-aws-karpenter-provider-aws-release-4.20-e2e-hypershift openshift/aws-karpenter-provider-aws presubmit Registry content changed
pull-ci-openshift-aws-karpenter-provider-aws-release-4.19-e2e-hypershift openshift/aws-karpenter-provider-aws presubmit Registry content changed
pull-ci-openshift-openstack-resource-controller-main-e2e-hypershift openshift/openstack-resource-controller presubmit Registry content changed
pull-ci-openshift-openstack-resource-controller-release-5.1-e2e-hypershift openshift/openstack-resource-controller presubmit Registry content changed
pull-ci-openshift-openstack-resource-controller-release-5.0-e2e-hypershift openshift/openstack-resource-controller presubmit Registry content changed
pull-ci-openshift-openstack-resource-controller-release-4.23-e2e-hypershift openshift/openstack-resource-controller presubmit Registry content changed
pull-ci-openshift-openstack-resource-controller-release-4.22-e2e-hypershift openshift/openstack-resource-controller presubmit Registry content changed
pull-ci-openshift-openstack-resource-controller-release-4.21-e2e-hypershift openshift/openstack-resource-controller presubmit Registry content changed
pull-ci-openshift-openstack-resource-controller-release-4.20-e2e-hypershift openshift/openstack-resource-controller presubmit Registry content changed
pull-ci-openshift-openstack-resource-controller-release-4.19-e2e-hypershift openshift/openstack-resource-controller presubmit Registry content changed
pull-ci-openshift-kubernetes-sigs-karpenter-release-4.23-e2e-hypershift openshift/kubernetes-sigs-karpenter presubmit Registry content changed
pull-ci-openshift-kubernetes-sigs-karpenter-release-4.21-e2e-hypershift openshift/kubernetes-sigs-karpenter presubmit Registry content changed
pull-ci-openshift-kubernetes-sigs-karpenter-release-4.20-e2e-hypershift openshift/kubernetes-sigs-karpenter presubmit Registry content changed
pull-ci-openshift-machine-config-operator-main-e2e-hypershift-techpreview openshift/machine-config-operator presubmit Registry content changed
pull-ci-openshift-machine-config-operator-main-e2e-openstack-hypershift openshift/machine-config-operator presubmit Registry content changed
pull-ci-openshift-machine-config-operator-release-5.1-e2e-hypershift-techpreview openshift/machine-config-operator presubmit Registry content changed
pull-ci-openshift-machine-config-operator-release-5.1-e2e-openstack-hypershift openshift/machine-config-operator presubmit Registry content changed
pull-ci-openshift-machine-config-operator-release-5.0-e2e-hypershift-techpreview openshift/machine-config-operator presubmit Registry content changed
pull-ci-openshift-machine-config-operator-release-5.0-e2e-openstack-hypershift openshift/machine-config-operator presubmit Registry content changed

A total of 157 jobs have been affected by this change. The above listing is non-exhaustive and limited to 25 jobs.

A full list of affected jobs can be found here

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.

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 8, 2026

@enxebre: all tests passed!

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.

@clebs
Copy link
Copy Markdown
Member

clebs commented May 9, 2026

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label May 9, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 9, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: clebs, csrwng, enxebre

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

The pull request process is described 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

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

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants