XML

Word

Printable

Type: Epic
Resolution: Done
Priority: Normal
Fix Version/s: openshift-4.16
Affects Version/s: None
Labels:
- aws
- karpenter
- research

Epic Name:
Karpenter PoC / v0
Work Type:
Upstream
Story Points:
8
Blocked:
False
Blocked Reason:
None
Ready:
False
Color Status:
Not Selected
Epic Status:
In Progress
Feature Link:
OCPSTRAT-1526 - [Upstream] Phase 1 : PoC for a new upstream CAPI provider for Karpenter on AWS- (part-1)
Parent Link:
OCPSTRAT-1526[Upstream] Phase 1 : PoC for a new upstream CAPI provider for Karpenter on AWS- (part-1)
Hierarchy Progress Bar:

60% To Do, 0% In Progress, 40% Done
Size:
XL

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

Intelligence Requested:
Market:

Epic Goal

Evaluate the viability of karpenter on OCP
Build a reference implementation
Compare with Cluster Auto-Scaler under the same test case

Why is this important?

Karpenter can be significant in saving costs for customers on AWS

Scenarios

Initial tests on AWS, replicating customer case

Acceptance Criteria

Karpenter deployed
Test cases executed in both karpenter and Cluster AutoScaler
Cost comparison and reports produced

Assignee:: Julio Faerman

Reporter:: Julio Faerman

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Created:: 2024/01/31 6:05 PM

Updated:: 2024/07/30 12:55 AM

Resolved:: 2024/05/13 2:29 PM