Loading...

XML

Word

Printable

Type: Epic
Resolution: Obsolete
Priority: Undefined
Fix Version/s: None
Affects Version/s: None
Component/s: AutoNode
Labels:
None

Epic Name:
Max NodeClaims cap for upstream Karpenter
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Ready:
False
Epic Status:
In Progress
Feature Link:
OCPSTRAT-2336 - [GA] AutoNode (Native Karpenter) with ROSA-HCP
Parent Link:
OCPSTRAT-2336[GA] AutoNode (Native Karpenter) with ROSA-HCP
Hierarchy Progress Bar:

0% To Do, 0% In Progress, 100% Done

SFDC Cases Links:
SFDC Cases Open:
SFDC Cases Counter:

Intelligence Requested:
Market:

Goal

Implement a max nodeclaims cap in the karpenter upstream project.

There is an existing issue created for this: https://github.com/kubernetes-sigs/karpenter/issues/2385

Why is this important?

This will allow us to solve the issue defined here: https://issues.redhat.com/browse/AUTOSCALE-292 without relying on an extra webhook controller in HyperShift control plane.

Acceptance Criteria

Dev
- RFC has been created upstream and approved
- Max cap functionality has been implemented upstream
- Downstream has cherry-picked or rebased on top of the new feature
- Remove any existing hack that was introduced by https://issues.redhat.com/browse/AUTOSCALE-292 that previously acted as a maximum nodeclaim limit for Karpenter in HCP

blocks

OCPSTRAT-2336 [GA] AutoNode (Native Karpenter) with ROSA-HCP

New

clones

AUTOSCALE-277 AutoNode disablement

New

duplicates

AUTOSCALE-292 Provide the Ability to Configure a Maximum Number of Nodes that can be Provisioned by Karpenter

In Progress

is related to

AUTOSCALE-292 Provide the Ability to Configure a Maximum Number of Nodes that can be Provisioned by Karpenter

In Progress

Assignee:: Unassigned

Reporter:: Max Cao

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Created:: 2025/08/27 8:27 PM

Updated:: 2025/09/10 10:30 PM

Resolved:: 2025/09/10 9:54 PM