Skip to content

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

Open
maxcao13 wants to merge 1 commit into
openshift:mainfrom
maxcao13:autonode-karpenter-provider-ci
Open

AUTOSCALE-681: update aws-karpenter-provider-aws configs#80128
maxcao13 wants to merge 1 commit into
openshift:mainfrom
maxcao13:autonode-karpenter-provider-ci

Conversation

@maxcao13
Copy link
Copy Markdown
Member

@maxcao13 maxcao13 commented Jun 4, 2026

Removes hypershift periodics in aws-karpenter-provider-aws. New periodics which cover the same code paths have been added to the hypershift repo for 4.22 and 5.0 here: #79262

Also updates the presubmits to match the new TestKarpenterUpgradeControlePlane suite, and allow them to run as multi-arch.

Summary by CodeRabbit

This PR updates the CI configuration for the AWS Karpenter Provider AWS repository, consolidating hypershift test coverage and enabling multi-architecture testing support.

Key Changes:

  1. Removes hypershift periodics: The e2e-hypershift periodic test entries and their associated hypershift base image references have been removed from release branch configurations (4.19–5.0 periodics). These tests are being consolidated into the hypershift repository's CI pipeline instead, as noted in PR #79262.

  2. Adds multi-architecture support: Both the main branch and release 4.22 configurations now define multi-arch release candidates (multi-initial and multi-latest) targeting the multi architecture with OCP nightly builds. This enables CI to test karpenter functionality across multiple architectures.

  3. Updates test configuration for multi-arch: The e2e-hypershift test configuration in the main and release-4.22 branches now:

    • Depends on the new multi-arch release candidates via OCP_IMAGE_LATEST and OCP_IMAGE_PREVIOUS mappings
    • Sets the AWS_MULTI_ARCH: "true" environment variable to enable multi-arch testing
    • Updates the CI_TESTS_RUN filter to ^TestKarpenter (matching the new test suite naming)
  4. Configuration cleanup: Release-4.21 adds a verify-deps test step with go-verify-deps to replace the removed hypershift tests.

Practical impact: The AWS Karpenter Provider AWS repository's CI pipeline now focuses on testing karpenter-specific functionality in multi-arch environments, while hypershift integration tests are maintained separately in the hypershift repository for better organizational clarity.

Signed-off-by: Max Cao <macao@redhat.com>
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jun 4, 2026

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 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 Jun 4, 2026
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jun 4, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

openshift-ci-robot commented Jun 4, 2026

@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:

Removes hypershift periodics in aws-karpenter-provider-aws. New periodics which cover the same code paths have been added to the hypershift repo for 4.22 and 5.0 here: #79262

Also updates the presubmits to match the new TestKarpenterUpgradeControlePlane suite, and allow them to run as multi-arch.

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 Jun 4, 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: 2f27bcd3-449f-4830-83a8-e0c278021f21

📥 Commits

Reviewing files that changed from the base of the PR and between a582d90 and 5cf1412.

⛔ Files ignored due to path filters (7)
  • ci-operator/jobs/openshift/aws-karpenter-provider-aws/openshift-aws-karpenter-provider-aws-release-4.19-periodics.yaml is excluded by !ci-operator/jobs/**
  • ci-operator/jobs/openshift/aws-karpenter-provider-aws/openshift-aws-karpenter-provider-aws-release-4.20-periodics.yaml is excluded by !ci-operator/jobs/**
  • ci-operator/jobs/openshift/aws-karpenter-provider-aws/openshift-aws-karpenter-provider-aws-release-4.21-periodics.yaml is excluded by !ci-operator/jobs/**
  • ci-operator/jobs/openshift/aws-karpenter-provider-aws/openshift-aws-karpenter-provider-aws-release-4.21-presubmits.yaml is excluded by !ci-operator/jobs/**
  • ci-operator/jobs/openshift/aws-karpenter-provider-aws/openshift-aws-karpenter-provider-aws-release-4.22-periodics.yaml is excluded by !ci-operator/jobs/**
  • ci-operator/jobs/openshift/aws-karpenter-provider-aws/openshift-aws-karpenter-provider-aws-release-4.23-periodics.yaml is excluded by !ci-operator/jobs/**
  • ci-operator/jobs/openshift/aws-karpenter-provider-aws/openshift-aws-karpenter-provider-aws-release-5.0-periodics.yaml is excluded by !ci-operator/jobs/**
📒 Files selected for processing (9)
  • ci-operator/config/openshift/aws-karpenter-provider-aws/openshift-aws-karpenter-provider-aws-main.yaml
  • ci-operator/config/openshift/aws-karpenter-provider-aws/openshift-aws-karpenter-provider-aws-release-4.19__periodics.yaml
  • ci-operator/config/openshift/aws-karpenter-provider-aws/openshift-aws-karpenter-provider-aws-release-4.20__periodics.yaml
  • ci-operator/config/openshift/aws-karpenter-provider-aws/openshift-aws-karpenter-provider-aws-release-4.21.yaml
  • ci-operator/config/openshift/aws-karpenter-provider-aws/openshift-aws-karpenter-provider-aws-release-4.21__periodics.yaml
  • ci-operator/config/openshift/aws-karpenter-provider-aws/openshift-aws-karpenter-provider-aws-release-4.22.yaml
  • ci-operator/config/openshift/aws-karpenter-provider-aws/openshift-aws-karpenter-provider-aws-release-4.22__periodics.yaml
  • ci-operator/config/openshift/aws-karpenter-provider-aws/openshift-aws-karpenter-provider-aws-release-4.23__periodics.yaml
  • ci-operator/config/openshift/aws-karpenter-provider-aws/openshift-aws-karpenter-provider-aws-release-5.0__periodics.yaml
💤 Files with no reviewable changes (7)
  • ci-operator/config/openshift/aws-karpenter-provider-aws/openshift-aws-karpenter-provider-aws-release-4.21.yaml
  • ci-operator/config/openshift/aws-karpenter-provider-aws/openshift-aws-karpenter-provider-aws-release-4.21__periodics.yaml
  • ci-operator/config/openshift/aws-karpenter-provider-aws/openshift-aws-karpenter-provider-aws-release-4.22__periodics.yaml
  • ci-operator/config/openshift/aws-karpenter-provider-aws/openshift-aws-karpenter-provider-aws-release-5.0__periodics.yaml
  • ci-operator/config/openshift/aws-karpenter-provider-aws/openshift-aws-karpenter-provider-aws-release-4.20__periodics.yaml
  • ci-operator/config/openshift/aws-karpenter-provider-aws/openshift-aws-karpenter-provider-aws-release-4.19__periodics.yaml
  • ci-operator/config/openshift/aws-karpenter-provider-aws/openshift-aws-karpenter-provider-aws-release-4.23__periodics.yaml

Walkthrough

This PR updates the AWS Karpenter provider CI configurations by introducing multi-arch release candidates (multi-initial and multi-latest) for main and 4.22 branches while systematically removing hypershift test support from all periodic and stable release configurations (4.19–5.0).

Changes

AWS Karpenter Provider CI Configuration

Layer / File(s) Summary
Multi-arch release candidates and e2e-hypershift test configuration
ci-operator/config/openshift/aws-karpenter-provider-aws/openshift-aws-karpenter-provider-aws-main.yaml, ci-operator/config/openshift/aws-karpenter-provider-aws/openshift-aws-karpenter-provider-aws-release-4.22.yaml
Adds multi-initial and multi-latest release candidates targeting OCP nightly stream version 5.0 (main) and 4.22; updates the e2e-hypershift test to depend on these multi-arch releases via OCP_IMAGE_LATEST/OCP_IMAGE_PREVIOUS, enables AWS_MULTI_ARCH: "true", sets RUN_KARPENTER_TESTS: true, and changes CI_TESTS_RUN to ^TestKarpenter.
Hypershift test removal from periodic release configurations
ci-operator/config/openshift/aws-karpenter-provider-aws/openshift-aws-karpenter-provider-aws-release-4.19__periodics.yaml, ci-operator/config/openshift/aws-karpenter-provider-aws/openshift-aws-karpenter-provider-aws-release-4.20__periodics.yaml, ci-operator/config/openshift/aws-karpenter-provider-aws/openshift-aws-karpenter-provider-aws-release-4.21__periodics.yaml, ci-operator/config/openshift/aws-karpenter-provider-aws/openshift-aws-karpenter-provider-aws-release-4.22__periodics.yaml, ci-operator/config/openshift/aws-karpenter-provider-aws/openshift-aws-karpenter-provider-aws-release-4.23__periodics.yaml, ci-operator/config/openshift/aws-karpenter-provider-aws/openshift-aws-karpenter-provider-aws-release-5.0__periodics.yaml
Removes the base_images block (hypershift-operator and hypershift-tests references) and the e2e-hypershift test entry from all periodic configurations, consolidating periodic test suites to e2e-aws only. The zz_generated_metadata section remains intact.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Possibly related PRs

  • openshift/release#79262: Both PRs introduce the release:multi-latest/release:multi-initial multi-arch image dependencies and update the corresponding hypershift e2e job environment to set AWS_MULTI_ARCH: "true" and CI_TESTS_RUN: ^TestKarpenter.

Suggested labels

lgtm, approved, rehearsals-ack

Suggested reviewers

  • devguyio
  • csrwng
🚥 Pre-merge checks | ✅ 15
✅ Passed checks (15 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'AUTOSCALE-681: update aws-karpenter-provider-aws configs' directly references the ticket and describes the main change: updating configuration files for the aws-karpenter-provider-aws component.
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 PR only modifies CI YAML config files, not test code. Custom check validates Ginkgo test names (It(), Describe()) in test source files, which are absent from this PR.
Test Structure And Quality ✅ Passed This PR contains only YAML CI/CD configuration files for aws-karpenter-provider-aws, not Ginkgo test code. The custom check for Ginkgo test structure is not applicable.
Microshift Test Compatibility ✅ Passed No new Ginkgo e2e tests are added. This PR only modifies CI configuration YAML files; test code is in the aws-karpenter-provider-aws source repository.
Single Node Openshift (Sno) Test Compatibility ✅ Passed PR modifies only CI configuration YAML files; no new Ginkgo e2e test code is added, making the SNO compatibility check not applicable.
Topology-Aware Scheduling Compatibility ✅ Passed PR modifies only CI operator test configurations, not deployment manifests, operator code, or controllers. Topology-aware scheduling check is not applicable.
Ote Binary Stdout Contract ✅ Passed OTE Binary Stdout Contract check is not applicable; PR only modifies YAML CI configuration files, not test source code.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed This PR only modifies CI configuration YAML files (67 files) for aws-karpenter-provider-aws. No new Ginkgo e2e tests are added, making the IPv6/disconnected network compatibility check not applicable.
No-Weak-Crypto ✅ Passed No weak cryptographic algorithms (MD5, SHA1, RC4, 3DES, Blowfish, ECB) found. All modified files are CI/CD YAML configuration files, not source code containing crypto implementations.
Container-Privileges ✅ Passed The PR modifies CI operator configuration files, not Kubernetes container manifests. No privileged settings found.
No-Sensitive-Data-In-Logs ✅ Passed PR contains only CI/CD YAML configuration changes with no logging statements or code that could expose sensitive data such as passwords, tokens, API keys, PII, or credentials.

✏️ 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 Jun 4, 2026
@openshift-merge-bot
Copy link
Copy Markdown
Contributor

[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-aws-karpenter-provider-aws-release-4.22-e2e-aws openshift/aws-karpenter-provider-aws presubmit Ci-operator config changed
pull-ci-openshift-aws-karpenter-provider-aws-release-4.22-e2e-hypershift openshift/aws-karpenter-provider-aws presubmit Ci-operator config changed
pull-ci-openshift-aws-karpenter-provider-aws-release-4.22-images openshift/aws-karpenter-provider-aws presubmit Ci-operator config changed
pull-ci-openshift-aws-karpenter-provider-aws-release-4.22-verify-deps openshift/aws-karpenter-provider-aws presubmit Ci-operator config changed
pull-ci-openshift-aws-karpenter-provider-aws-release-4.21-e2e-aws openshift/aws-karpenter-provider-aws presubmit Ci-operator config changed
pull-ci-openshift-aws-karpenter-provider-aws-release-4.21-images openshift/aws-karpenter-provider-aws presubmit Ci-operator config changed
pull-ci-openshift-aws-karpenter-provider-aws-release-4.21-okd-scos-e2e-aws-ovn openshift/aws-karpenter-provider-aws presubmit Ci-operator config changed
pull-ci-openshift-aws-karpenter-provider-aws-release-4.21-okd-scos-images openshift/aws-karpenter-provider-aws presubmit Ci-operator config changed
pull-ci-openshift-aws-karpenter-provider-aws-release-4.21-verify-deps openshift/aws-karpenter-provider-aws presubmit Ci-operator config changed
pull-ci-openshift-aws-karpenter-provider-aws-main-e2e-aws openshift/aws-karpenter-provider-aws presubmit Ci-operator config changed
pull-ci-openshift-aws-karpenter-provider-aws-main-e2e-hypershift openshift/aws-karpenter-provider-aws presubmit Ci-operator config changed
pull-ci-openshift-aws-karpenter-provider-aws-main-images openshift/aws-karpenter-provider-aws presubmit Ci-operator config changed
pull-ci-openshift-aws-karpenter-provider-aws-main-okd-scos-e2e-aws-ovn openshift/aws-karpenter-provider-aws presubmit Ci-operator config changed
pull-ci-openshift-aws-karpenter-provider-aws-main-okd-scos-images openshift/aws-karpenter-provider-aws presubmit Ci-operator config changed
pull-ci-openshift-aws-karpenter-provider-aws-main-verify-deps openshift/aws-karpenter-provider-aws presubmit Ci-operator config changed
periodic-ci-openshift-aws-karpenter-provider-aws-release-4.21-periodics-e2e-aws N/A periodic Ci-operator config changed
periodic-ci-openshift-aws-karpenter-provider-aws-release-4.20-periodics-e2e-aws N/A periodic Ci-operator config changed
periodic-ci-openshift-aws-karpenter-provider-aws-main-periodics-rebasebot N/A periodic Ci-operator config changed
periodic-ci-openshift-aws-karpenter-provider-aws-release-5.0-periodics-e2e-aws N/A periodic Ci-operator config changed
periodic-ci-openshift-aws-karpenter-provider-aws-release-4.19-periodics-e2e-aws N/A periodic Ci-operator config changed
periodic-ci-openshift-aws-karpenter-provider-aws-release-4.23-periodics-e2e-aws N/A periodic Ci-operator config changed
periodic-ci-openshift-aws-karpenter-provider-aws-release-4.22-periodics-e2e-aws N/A periodic Ci-operator config changed

Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals.

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.

@maxcao13
Copy link
Copy Markdown
Member Author

maxcao13 commented Jun 4, 2026

/pj-rehearse pull-ci-openshift-aws-karpenter-provider-aws-main-e2e-hypershift pull-ci-openshift-aws-karpenter-provider-aws-release-4.22-e2e-hypershift

@openshift-merge-bot
Copy link
Copy Markdown
Contributor

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

@maxcao13 maxcao13 marked this pull request as ready for review June 5, 2026 20:17
@openshift-ci 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 5, 2026
@openshift-ci openshift-ci Bot requested review from joelsmith and muraee June 5, 2026 20:18
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jun 5, 2026

@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/openshift/aws-karpenter-provider-aws/release-4.22/e2e-hypershift 5cf1412 link unknown /pj-rehearse pull-ci-openshift-aws-karpenter-provider-aws-release-4.22-e2e-hypershift

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.

Copy link
Copy Markdown
Contributor

@elmiko elmiko left a comment

Choose a reason for hiding this comment

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

i'm not 100% sure on the environment variable additions, but the periodic removals look ok to me.

/lgtm

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

openshift-ci Bot commented Jun 5, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: elmiko, 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:

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

@elmiko
Copy link
Copy Markdown
Contributor

elmiko commented Jun 5, 2026

might have jumped the gun, seems like there is an issue with one of the e2es.

do you think this is related to the PR @maxcao13 ?

@maxcao13
Copy link
Copy Markdown
Member Author

maxcao13 commented Jun 5, 2026

No, it's related to one of the bug that john merged openshift/hypershift#8562 but hasn't backported to 4.22 yet: openshift/hypershift#8632

We saw this failure in this other hypershift release config fixup PR here: #79262

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

3 participants