AUTOSCALE-681: Add AutoNode multi-arch periodic to HCP by maxcao13 · Pull Request #79262 · openshift/release

maxcao13 · 2026-05-13T17:28:28Z

Also adjust autonode presubmit to include all Karpenter tests, make it multi-arch, and remove the TechPreview gate on the hypershift-operator when exercising those tests.

Overview

This PR updates the OpenShift CI configuration in the openshift/release repository to enable multi-architecture AutoNode (Karpenter) testing for Hypershift and to add a periodic multi-arch AutoNode job across recent release branches.

What changed (practical impact)

Repository area affected: ci-operator configuration for openshift/hypershift (OpenShift CI job definitions and periodic job configs).
Purpose: run the Karpenter AutoNode e2e tests against multi-arch release images and schedule periodic multi-arch validation.

Key changes

Multi-arch release candidates (openshift-hypershift-main.yaml)
- Added release image candidates "multi-initial" and "multi-latest" (product: ocp, architecture: multi, version: "5.0"). Enables CI to reference multi-architecture release images.
e2e-aws-autonode presubmit (openshift-hypershift-main.yaml)
- Switched job to use multi-arch release image references (OCP_IMAGE_LATEST: release:multi-latest, OCP_IMAGE_PREVIOUS: release:multi-initial).
- Enabled multi-arch testing via AWS_MULTI_ARCH: "true".
- Adjusted test selection to run the Karpenter suite using CI_TESTS_RUN: ^TestKarpenter (pattern simplified).
- Removed the TECH_PREVIEW_NO_UPGRADE environment variable.
New periodic jobs (release branch periodics)
- Added an e2e-aws-autonode periodic (cron: 0 */12 * * *) to the periodics for:
  - openshift-hypershift-release-4.22__periodics.yaml
  - openshift-hypershift-release-4.23__periodics.yaml
  - openshift-hypershift-release-5.0__periodics.yaml
- Each periodic uses hypershift-aws cluster profile, depends on the multi-arch release candidates, sets AWS_MULTI_ARCH: "true", and runs the Karpenter test suite via the hypershift-aws-e2e-nested workflow.

Test / rehearsal activity and known issues

The PR author invoked rehearsals for the presubmit and periodics (/pj-rehearse ...).
An ARM failure was observed in rehearsals: quay.io/openshift/origin-pod appears to have only an amd64 manifest and fails on ARM nodes. The author plans a follow-up HCP PR to select a different image for ARM compatibility.

Robot feedback

openshift-ci-robot confirmed the PR references AUTOSCALE-681 but warned the referenced Jira issue lacks a target version; the expected target version for the target branch is "5.0.0". The robot provided links for prow command help and filing issues against the jira-lifecycle-plugin.

Impact

Enables CI to exercise AutoNode/Karpenter workflows against multi-architecture release images across main and release branches, improving multi-arch coverage.
A follow-up change is required to fix the ARM image pull issue (replace quay.io/openshift/origin-pod with an ARM-capable image) before full ARM validation will succeed.

Files touched (high-level)

ci-operator/config/openshift/hypershift/openshift-hypershift-main.yaml
ci-operator/config/openshift/hypershift/openshift-hypershift-release-4.22__periodics.yaml
ci-operator/config/openshift/hypershift/openshift-hypershift-release-4.23__periodics.yaml
ci-operator/config/openshift/hypershift/openshift-hypershift-release-5.0__periodics.yaml

openshift-ci · 2026-05-13T17:28:32Z

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-robot · 2026-05-13T17:28:33Z

@maxcao13: This pull request references AUTOSCALE-681 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:

Also adjust autonode presubmit to include all Karpenter tests, multi-arch, remove TP.

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 · 2026-05-13T17:28:54Z

Walkthrough

The PR enables multi-architecture (AMD64 + ARM64) AWS autonode testing for HyperShift by introducing multi-arch release definitions in the main configuration and adding periodic test jobs for three OpenShift releases (4.22, 4.23, 5.0) that consume these releases.

Changes

Multi-Arch AWS Autonode Testing

Layer / File(s)	Summary
Multi-arch release definitions `ci-operator/config/openshift/hypershift/openshift-hypershift-main.yaml`	Two new release entries `multi-initial` and `multi-latest` are defined with `architecture: multi`, `version: "5.0"`, and `stream: nightly` to provide multi-arch OCP images for testing.
Updated main test job for multi-arch `ci-operator/config/openshift/hypershift/openshift-hypershift-main.yaml`	The `e2e-aws-autonode` test job is reconfigured to use `OCP_IMAGE_LATEST: release:multi-latest` and `OCP_IMAGE_PREVIOUS: release:multi-initial`, sets `AWS_MULTI_ARCH: "true"`, updates `CI_TESTS_RUN` to match `^TestKarpenter`, and removes `TECH_PREVIEW_NO_UPGRADE`.
Periodic test jobs across releases `ci-operator/config/openshift/hypershift/openshift-hypershift-release-4.22__periodics.yaml`, `ci-operator/config/openshift/hypershift/openshift-hypershift-release-4.23__periodics.yaml`, `ci-operator/config/openshift/hypershift/openshift-hypershift-release-5.0__periodics.yaml`	Three new periodic test entries named `e2e-aws-autonode` are added with `0 /12 * *` cron schedule, `hypershift-aws` cluster profile, dependencies on the multi-arch releases, environment variables for multi-arch AWS and Karpenter testing, and `hypershift-aws-e2e-nested` workflow.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Suggested labels: lgtm, approved, rehearsals-ack

Suggested reviewers:

muraee
Nirshal
joelsmith

🚥 Pre-merge checks | ✅ 12

✅ Passed checks (12 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the main changes: adding multi-arch periodic tests for AutoNode to HyperShift with Karpenter support.
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	Check not applicable. PR modifies YAML CI configuration files and utility tools, not Ginkgo test definitions. No Ginkgo test names (It, Describe, etc.) with dynamic information were added or modified.
Test Structure And Quality	✅ Passed	Check not applicable: PR modifies only YAML CI/CD configuration files, not Ginkgo test code. Custom check requires Ginkgo test structure review.
Microshift Test Compatibility	✅ Passed	This PR modifies only CI configuration YAML files and does not add any new Ginkgo e2e test code. The check is not applicable to CI configuration-only changes.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	No new Ginkgo test code added; only CI configuration YAML files modified.
Topology-Aware Scheduling Compatibility	✅ Passed	PR contains only CI operator config files defining test workflows and image releases, not deployment manifests. No Kubernetes scheduling constraints present.
Ote Binary Stdout Contract	✅ Passed	PR modifies only CI operator configuration files (YAML), not Go test source code. The OTE Binary Stdout Contract check applies to Go binaries; this PR contains no test source code changes.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	PR does not add new Ginkgo e2e test code; it only modifies CI configuration files. The check for IPv6/disconnected network test compatibility is not applicable to CI configuration changes.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ 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.}

maxcao13 · 2026-05-13T17:36:20Z

/pj-rehearse pull-ci-openshift-hypershift-main-e2e-aws pull-ci-openshift-hypershift-main-e2e-aws-autonode periodic-ci-openshift-hypershift-release-5.0-periodics-e2e-aws-autonode periodic-ci-openshift-hypershift-release-4.22-periodics-e2e-aws-autonode

openshift-merge-bot · 2026-05-13T17:36:22Z

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

maxcao13 · 2026-05-13T21:56:11Z

Well seems like the arm test is failing, so gonna investigate that.

maxcao13 · 2026-05-13T22:44:47Z

Seems like quay.io/openshift/origin-pod only has an amd64 manifest, so the node can't pull it. I'm not sure why I thought this was working before. I will put in an hcp PR to select a different image.

maxcao13 · 2026-05-15T16:54:50Z

Now that openshift/hypershift#8510 has merged, theoretically these should now all pass:

/pj-rehearse pull-ci-openshift-hypershift-main-e2e-aws pull-ci-openshift-hypershift-main-e2e-aws-autonode periodic-ci-openshift-hypershift-release-5.0-periodics-e2e-aws-autonode periodic-ci-openshift-hypershift-release-4.22-periodics-e2e-aws-autonode

openshift-merge-bot · 2026-05-15T16:54:52Z

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

openshift-ci-robot · 2026-05-15T16:55:22Z

@maxcao13: This pull request references AUTOSCALE-681 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 task to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Also adjust autonode presubmit to include all Karpenter tests, multi-arch, remove TP.

Overview

This PR updates the OpenShift CI configuration in the openshift/release repository to enable multi-architecture AutoNode (Karpenter) testing for Hypershift and to add a periodic multi-arch AutoNode job across recent release branches.

What changed (practical impact)

Repository area affected: ci-operator configuration for openshift/hypershift (OpenShift CI job definitions and periodic job configs).

Purpose: run the Karpenter AutoNode e2e tests against multi-arch release images and schedule periodic multi-arch validation.

Key changes

Multi-arch release candidates (openshift-hypershift-main.yaml)

Added release image candidates "multi-initial" and "multi-latest" (product: ocp, architecture: multi, version: "5.0"). Enables CI to reference multi-architecture release images.

e2e-aws-autonode presubmit (openshift-hypershift-main.yaml)

Switched job to use multi-arch release image references (OCP_IMAGE_LATEST: release:multi-latest, OCP_IMAGE_PREVIOUS: release:multi-initial).

Enabled multi-arch testing via AWS_MULTI_ARCH: "true".

Adjusted test selection to run the Karpenter suite using CI_TESTS_RUN: ^TestKarpenter (pattern simplified).

Removed the TECH_PREVIEW_NO_UPGRADE environment variable.

New periodic jobs (release branch periodics)

Added an e2e-aws-autonode periodic (cron: 0 */12 * * *) to the periodics for:

openshift-hypershift-release-4.22__periodics.yaml

openshift-hypershift-release-4.23__periodics.yaml

openshift-hypershift-release-5.0__periodics.yaml

Each periodic uses hypershift-aws cluster profile, depends on the multi-arch release candidates, sets AWS_MULTI_ARCH: "true", and runs the Karpenter test suite via the hypershift-aws-e2e-nested workflow.

Test / rehearsal activity and known issues

The PR author invoked rehearsals for the presubmit and periodics (/pj-rehearse ...).

An ARM failure was observed in rehearsals: quay.io/openshift/origin-pod appears to have only an amd64 manifest and fails on ARM nodes. The author plans a follow-up HCP PR to select a different image for ARM compatibility.

Robot feedback

openshift-ci-robot confirmed the PR references AUTOSCALE-681 but warned the referenced Jira issue lacks a target version; the expected target version for the target branch is "5.0.0". The robot provided links for prow command help and filing issues against the jira-lifecycle-plugin.

Impact

Enables CI to exercise AutoNode/Karpenter workflows against multi-architecture release images across main and release branches, improving multi-arch coverage.

A follow-up change is required to fix the ARM image pull issue (replace quay.io/openshift/origin-pod with an ARM-capable image) before full ARM validation will succeed.

Files touched (high-level)

ci-operator/config/openshift/hypershift/openshift-hypershift-main.yaml

ci-operator/config/openshift/hypershift/openshift-hypershift-release-4.22__periodics.yaml

ci-operator/config/openshift/hypershift/openshift-hypershift-release-4.23__periodics.yaml

ci-operator/config/openshift/hypershift/openshift-hypershift-release-5.0__periodics.yaml

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.

maxcao13 · 2026-05-21T16:50:03Z

/pj-rehearse pull-ci-openshift-hypershift-main-e2e-aws pull-ci-openshift-hypershift-main-e2e-aws-autonode periodic-ci-openshift-hypershift-release-5.0-periodics-e2e-aws-autonode periodic-ci-openshift-hypershift-release-4.22-periodics-e2e-aws-autonode

openshift-merge-bot · 2026-05-21T16:50:06Z

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

maxcao13 · 2026-05-21T19:30:16Z

/pj-rehearse pull-ci-openshift-hypershift-main-e2e-aws-autonode pull-ci-openshift-hypershift-main-e2e-aws periodic-ci-openshift-hypershift-release-4.22-periodics-e2e-aws-autonode

Flaky.

openshift-merge-bot · 2026-05-21T19:30:20Z

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

maxcao13 · 2026-05-21T22:58:54Z

/pj-rehearse periodic-ci-openshift-hypershift-release-4.22-periodics-e2e-aws-autonode pull-ci-openshift-hypershift-main-e2e-aws

openshift-merge-bot · 2026-05-21T22:58:57Z

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

maxcao13 · 2026-05-29T16:52:03Z

/pj-rehearse pull-ci-openshift-hypershift-main-e2e-aws pull-ci-openshift-hypershift-main-e2e-aws-autonode periodic-ci-openshift-hypershift-release-5.0-periodics-e2e-aws-autonode periodic-ci-openshift-hypershift-release-4.22-periodics-e2e-aws-autonode

openshift-merge-bot · 2026-05-29T16:52:07Z

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

maxcao13 · 2026-05-29T19:18:57Z

/pj-rehearse pull-ci-openshift-hypershift-main-e2e-aws periodic-ci-openshift-hypershift-release-4.22-periodics-e2e-aws-autonode

openshift-merge-bot · 2026-05-29T19:19:00Z

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

maxcao13 · 2026-06-01T15:55:29Z

/pj-rehearse pull-ci-openshift-hypershift-main-e2e-aws periodic-ci-openshift-hypershift-release-4.22-periodics-e2e-aws-autonode

Infra again.

openshift-merge-bot · 2026-06-01T15:55:32Z

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

maxcao13 · 2026-06-02T15:53:59Z

/pj-rehearse periodic-ci-openshift-hypershift-release-4.22-periodics-e2e-aws-autonode

openshift-merge-bot · 2026-06-02T15:54:02Z

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

openshift-merge-bot · 2026-06-02T18:00:28Z

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

openshift-ci · 2026-06-03T22:00:37Z

@maxcao13: 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-hypershift-release-4.22-periodics-e2e-aws-autonode	`8d9f09e`	link	unknown	`/pj-rehearse periodic-ci-openshift-hypershift-release-4.22-periodics-e2e-aws-autonode`

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.

Also adjust autonode presubmit to include all Karpenter tests, multi-arch, remove TP. Signed-off-by: Max Cao <macao@redhat.com>

openshift-merge-bot · 2026-06-04T01:48:16Z

[REHEARSALNOTIFIER]
@maxcao13: 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-hypershift-main-address-review-comments	openshift/hypershift	presubmit	Ci-operator config changed
pull-ci-openshift-hypershift-main-agentic-qe-aws	openshift/hypershift	presubmit	Ci-operator config changed
pull-ci-openshift-hypershift-main-e2e-agent-connected-ovn-ipv4-metal-backuprestore	openshift/hypershift	presubmit	Ci-operator config changed
pull-ci-openshift-hypershift-main-e2e-aks	openshift/hypershift	presubmit	Ci-operator config changed
pull-ci-openshift-hypershift-main-e2e-aks-4-22	openshift/hypershift	presubmit	Ci-operator config changed
pull-ci-openshift-hypershift-main-e2e-aks-override	openshift/hypershift	presubmit	Ci-operator config changed
pull-ci-openshift-hypershift-main-e2e-aws	openshift/hypershift	presubmit	Ci-operator config changed
pull-ci-openshift-hypershift-main-e2e-aws-4-22	openshift/hypershift	presubmit	Ci-operator config changed
pull-ci-openshift-hypershift-main-e2e-aws-autonode	openshift/hypershift	presubmit	Ci-operator config changed
pull-ci-openshift-hypershift-main-e2e-aws-external-oidc-techpreview	openshift/hypershift	presubmit	Ci-operator config changed
pull-ci-openshift-hypershift-main-e2e-aws-metrics	openshift/hypershift	presubmit	Ci-operator config changed
pull-ci-openshift-hypershift-main-e2e-aws-minimal	openshift/hypershift	presubmit	Ci-operator config changed
pull-ci-openshift-hypershift-main-e2e-aws-override	openshift/hypershift	presubmit	Ci-operator config changed
pull-ci-openshift-hypershift-main-e2e-aws-techpreview	openshift/hypershift	presubmit	Ci-operator config changed
pull-ci-openshift-hypershift-main-e2e-aws-upgrade-hypershift-operator	openshift/hypershift	presubmit	Ci-operator config changed
pull-ci-openshift-hypershift-main-e2e-azure-aks-external-oidc-techpreview	openshift/hypershift	presubmit	Ci-operator config changed
pull-ci-openshift-hypershift-main-e2e-azure-aks-ovn-conformance	openshift/hypershift	presubmit	Ci-operator config changed
pull-ci-openshift-hypershift-main-e2e-azure-kubevirt-ovn	openshift/hypershift	presubmit	Ci-operator config changed
pull-ci-openshift-hypershift-main-e2e-azure-self-managed	openshift/hypershift	presubmit	Ci-operator config changed
pull-ci-openshift-hypershift-main-e2e-azure-v2-self-managed	openshift/hypershift	presubmit	Ci-operator config changed
pull-ci-openshift-hypershift-main-e2e-conformance	openshift/hypershift	presubmit	Ci-operator config changed
pull-ci-openshift-hypershift-main-e2e-kubevirt-aws-ovn	openshift/hypershift	presubmit	Ci-operator config changed
pull-ci-openshift-hypershift-main-e2e-kubevirt-aws-ovn-reduced	openshift/hypershift	presubmit	Ci-operator config changed
pull-ci-openshift-hypershift-main-e2e-kubevirt-azure-ovn	openshift/hypershift	presubmit	Ci-operator config changed
pull-ci-openshift-hypershift-main-e2e-kubevirt-metal-ovn-backuprestore	openshift/hypershift	presubmit	Ci-operator config changed

A total of 48 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.

enxebre · 2026-06-04T07:27:32Z

/lgtm

openshift-ci · 2026-06-04T07:28:48Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: enxebre, maxcao13

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:

~~ci-operator/config/openshift/hypershift/OWNERS~~ [enxebre]
~~ci-operator/jobs/openshift/hypershift/OWNERS~~ [enxebre]

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

maxcao13 · 2026-06-04T15:56:45Z

/pj-rehearse ack

There is no tide status, so I hope this works?

openshift-merge-bot · 2026-06-04T15:56:48Z

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

…penshift#79262) Also adjust autonode presubmit to include all Karpenter tests, multi-arch, remove TP. Signed-off-by: Max Cao <macao@redhat.com>

openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 13, 2026

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 May 13, 2026

maxcao13 changed the title ~~AUTOSCALE-681: Add AutoNode multi-arch periodic~~ AUTOSCALE-681: Add AutoNode multi-arch periodic to HCP May 13, 2026

maxcao13 force-pushed the hcp-autonode-fix branch from e62bf6a to 293fe9c Compare May 15, 2026 16:53

maxcao13 mentioned this pull request May 15, 2026

NO-JIRA: fix(e2e): use public multi-arch image for ARM64 karpenter test openshift/hypershift#8532

Merged

4 tasks

maxcao13 force-pushed the hcp-autonode-fix branch from 293fe9c to 8d9f09e Compare May 29, 2026 16:48

maxcao13 marked this pull request as ready for review June 3, 2026 21:47

openshift-ci Bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jun 3, 2026

openshift-ci Bot requested review from csrwng and devguyio June 3, 2026 21:47

maxcao13 force-pushed the hcp-autonode-fix branch from 8d9f09e to 8197e76 Compare June 3, 2026 21:54

test(hcp-autonode): Add AutoNode multi-arch periodics for 4.22/5.0

ce60503

Also adjust autonode presubmit to include all Karpenter tests, multi-arch, remove TP. Signed-off-by: Max Cao <macao@redhat.com>

maxcao13 force-pushed the hcp-autonode-fix branch from 8197e76 to ce60503 Compare June 4, 2026 01:45

openshift-ci Bot assigned enxebre Jun 4, 2026

openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jun 4, 2026

openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 4, 2026

openshift-merge-bot Bot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Jun 4, 2026

openshift-merge-bot Bot merged commit 857a717 into openshift:main Jun 4, 2026
16 checks passed

maxcao13 deleted the hcp-autonode-fix branch June 4, 2026 16:47

maxcao13 mentioned this pull request Jun 4, 2026

AUTOSCALE-681: update aws-karpenter-provider-aws configs #80128

Merged

This was referenced Jun 8, 2026

OCPBUGS-86964: Test e2e-kubevirt-aws-ovn-gpu with hypershift-aws profile #80145

Merged

Revert "hypershift: resolve nodepool releases at runtime" (#79627) #80349

Merged

Uh oh!

Conversation

maxcao13 commented May 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Overview

What changed (practical impact)

Key changes

Test / rehearsal activity and known issues

Robot feedback

Impact

Files touched (high-level)

Uh oh!

openshift-ci Bot commented May 13, 2026

Uh oh!

openshift-ci-robot commented May 13, 2026 • edited by atlassian Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

coderabbitai Bot commented May 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Changes

Estimated code review effort

Uh oh!

maxcao13 commented May 13, 2026

Uh oh!

openshift-merge-bot Bot commented May 13, 2026

Uh oh!

maxcao13 commented May 13, 2026

Uh oh!

maxcao13 commented May 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

maxcao13 commented May 15, 2026

Uh oh!

openshift-merge-bot Bot commented May 15, 2026

Uh oh!

openshift-ci-robot commented May 15, 2026 • edited by atlassian Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Overview

What changed (practical impact)

Key changes

Test / rehearsal activity and known issues

Robot feedback

Impact

Files touched (high-level)

Uh oh!

maxcao13 commented May 21, 2026

Uh oh!

openshift-merge-bot Bot commented May 21, 2026

Uh oh!

maxcao13 commented May 21, 2026

Uh oh!

openshift-merge-bot Bot commented May 21, 2026

Uh oh!

maxcao13 commented May 21, 2026

Uh oh!

openshift-merge-bot Bot commented May 21, 2026

Uh oh!

maxcao13 commented May 29, 2026

Uh oh!

openshift-merge-bot Bot commented May 29, 2026

Uh oh!

maxcao13 commented May 29, 2026

Uh oh!

openshift-merge-bot Bot commented May 29, 2026

Uh oh!

maxcao13 commented Jun 1, 2026

Uh oh!

openshift-merge-bot Bot commented Jun 1, 2026

Uh oh!

maxcao13 commented Jun 2, 2026

Uh oh!

openshift-merge-bot Bot commented Jun 2, 2026

Uh oh!

openshift-merge-bot Bot commented Jun 2, 2026

Uh oh!

openshift-ci Bot commented Jun 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-merge-bot Bot commented Jun 4, 2026

maxcao13 commented May 13, 2026 •

edited

Loading

openshift-ci-robot commented May 13, 2026 •

edited by atlassian Bot

Loading

coderabbitai Bot commented May 13, 2026 •

edited

Loading

maxcao13 commented May 13, 2026 •

edited

Loading

openshift-ci-robot commented May 15, 2026 •

edited by atlassian Bot

Loading

openshift-ci Bot commented Jun 3, 2026 •

edited

Loading