AUTOSCALE-681: Add AutoNode multi-arch periodic to HCP#79262
Conversation
Also adjust autonode presubmit to include all Karpenter tests, multi-arch, remove TP. Signed-off-by: Max Cao <macao@redhat.com>
|
Skipping CI for Draft Pull Request. |
openshift-ci-robot
added
the
jira/valid-reference
openshift-ci
Bot
added
the
do-not-merge/work-in-progress
|
@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. DetailsIn response to this:
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
changed the title
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited) Review profile: CHILL Plan: Enterprise Run ID: ⛔ Files ignored due to path filters (3)
📒 Files selected for processing (4)
WalkthroughThe 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. ChangesMulti-Arch AWS Autonode Testing
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes 🚥 Pre-merge checks | ✅ 12✅ Passed checks (12 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: maxcao13 The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
[REHEARSALNOTIFIER]
A total of 46 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-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
/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 |
|
@maxcao13: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
@maxcao13: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
Well seems like the arm test is failing, so gonna investigate that. |
|
Seems like quay.io/openshift/origin-pod only has an amd64 manifest, so it 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. |
2 participants
Also adjust autonode presubmit to include all Karpenter tests, multi-arch, remove TP.
Overview
This PR adds multi-arch support for AutoNode/Karpenter testing in the OpenShift hypershift repository's CI infrastructure, and establishes periodic jobs to validate AutoNode functionality across multiple OpenShift release branches.
Changes to Hypershift CI Configuration
Multi-arch release definitions (
openshift-hypershift-main.yaml):multi-initialandmulti-latestrelease image candidates targeting OCP 5.0 with multi-architecture supportUpdated e2e-aws-autonode presubmit test (
openshift-hypershift-main.yaml):OCP_IMAGE_LATESTandOCP_IMAGE_PREVIOUS)AWS_MULTI_ARCH: "true"^TestKarpenterpatternTECH_PREVIEW_NO_UPGRADE)New periodic test jobs:
Adds
e2e-aws-autonodeperiodic test jobs running every 12 hours across three release branches:openshift-hypershift-release-4.22__periodics.yamlopenshift-hypershift-release-4.23__periodics.yamlopenshift-hypershift-release-5.0__periodics.yamlEach periodic job uses the hypershift AWS cluster profile, runs full Karpenter test suite (
^TestKarpenter), and validates multi-arch AutoNode functionality with hypershift feature flags enabled.Impact
Enables continuous multi-architecture testing of AutoNode and Karpenter functionality in hypershift across recent and future OpenShift release branches, improving confidence in AutoNode compatibility across diverse architectures.