Skip to content

WIP: AUTOSCALE-485: bump karpenter-aws dependencies to 1.9.0#7743

Draft
maxcao13 wants to merge 1 commit intoopenshift:mainfrom
maxcao13:karpenter-1.9.0
Draft

WIP: AUTOSCALE-485: bump karpenter-aws dependencies to 1.9.0#7743
maxcao13 wants to merge 1 commit intoopenshift:mainfrom
maxcao13:karpenter-1.9.0

Conversation

@maxcao13
Copy link
Member

@maxcao13 maxcao13 commented Feb 18, 2026

What this PR does / why we need it:

Bumps karpenter deps to 1.9.0 for core library and 1.9.0 for aws provider. Updates replaced directive to point to our recently rebased downstream repos.

Also syncs karpenter CRDS and adjusts the cel validations:

  • ./hacks/crds-sync.sh
  • ./karpenter-operator/controllers/karpenter/assets/adjust-cel.sh

Which issue(s) this PR fixes:

Fixes AUTOSCALE-485

Special notes for your reviewer:

Checklist:

  • Subject and description added to both, commit and PR.
  • Relevant issues have been referenced.
  • This change includes docs.
  • This change includes unit tests.

@openshift-ci-robot
Copy link

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

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

openshift-ci-robot commented Feb 18, 2026

@maxcao13: This pull request references AUTOSCALE-485 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 "4.22.0" version, but no target version was set.

Details

In response to this:

What this PR does / why we need it:

Bumps karpenter deps to 1.9.0 for core library and 1.9.0 for aws provider. Updates replaced directive to point to our recently rebased downstream repos.

Also syncs karpenter CRDS and adjusts the cel validations:

  • ./hacks/crds-sync.sh
  • ./karpenter-operator/controllers/karpenter/assets/adjust-cel.sh

Which issue(s) this PR fixes:

Fixes AUTOSCALE-485

Special notes for your reviewer:

Checklist:

  • Subject and description added to both, commit and PR.
  • Relevant issues have been referenced.
  • This change includes docs.
  • This change includes unit tests.

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
Contributor

coderabbitai bot commented Feb 18, 2026

Important

Review skipped

Auto reviews are limited based on label configuration.

🚫 Review skipped — only excluded labels are configured. (1)
  • do-not-merge/work-in-progress

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

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

@openshift-ci openshift-ci bot added do-not-merge/needs-area do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. labels Feb 18, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 18, 2026

@maxcao13: This pull request references AUTOSCALE-485 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 "4.22.0" version, but no target version was set.

Details

In response to this:

What this PR does / why we need it:

Bumps karpenter deps to 1.9.0 for core library and 1.9.0 for aws provider. Updates replaced directive to point to our recently rebased downstream repos.

Also syncs karpenter CRDS and adjusts the cel validations:

  • ./hacks/crds-sync.sh
  • ./karpenter-operator/controllers/karpenter/assets/adjust-cel.sh

Which issue(s) this PR fixes:

Fixes AUTOSCALE-485

Special notes for your reviewer:

Checklist:

  • Subject and description added to both, commit and PR.
  • Relevant issues have been referenced.
  • This change includes docs.
  • This change includes unit tests.

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
Copy link
Contributor

openshift-ci bot commented Feb 18, 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

@maxcao13
Copy link
Member Author

/area api karpenter-operator

@openshift-ci openshift-ci bot added the area/api Indicates the PR includes changes for the API label Feb 18, 2026
Bumps karpenter deps to 1.9.0 for core library and 1.9.0 for aws provider.
Updates replaced directive to point to our recently rebased downstream repos.

Also syncs karpenter CRDS and adjusts the cel validations:
- ./hacks/crds-sync.sh
- ./karpenter-operator/controllers/karpenter/assets/adjust-cel.sh

Signed-off-by: Max Cao <macao@redhat.com>
@openshift-ci openshift-ci bot added area/karpenter-operator Indicates the PR includes changes related to the Karpenter operator and removed do-not-merge/needs-area labels Feb 18, 2026
@maxcao13
Copy link
Member Author

/test e2e-aws-techpreview

@openshift-ci openshift-ci bot added area/platform/aws PR/issue for AWS (AWSPlatform) platform area/platform/azure PR/issue for Azure (AzurePlatform) platform labels Feb 18, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 18, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

1 similar comment
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 18, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: maxcao13
Once this PR has been reviewed and has the lgtm label, please assign bryan-cox 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
Copy link
Contributor

openshift-ci bot commented Feb 18, 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/prow/e2e-aws-techpreview 053d3a5 link false /test e2e-aws-techpreview

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.

@maxcao13
Copy link
Member Author

/hold

This has to wait for hypershift to bump to 0.35 k8s deps. There are some breaking changes here that I probably shouldn't try to resolve myself.

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 18, 2026
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 21, 2026
@openshift-merge-robot
Copy link
Contributor

PR needs rebase.

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.

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

Labels

area/api Indicates the PR includes changes for the API area/karpenter-operator Indicates the PR includes changes related to the Karpenter operator area/platform/aws PR/issue for AWS (AWSPlatform) platform area/platform/azure PR/issue for Azure (AzurePlatform) platform do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. 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. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants