Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Integrate with Karpenter #1114

Open
t0yv0 opened this issue Apr 3, 2024 · 3 comments
Open

Integrate with Karpenter #1114

t0yv0 opened this issue Apr 3, 2024 · 3 comments
Labels
kind/enhancement Improvements or new features size/L Estimated effort to complete (up to 10 days).

Comments

@t0yv0
Copy link
Member

t0yv0 commented Apr 3, 2024

Hello!

  • Vote on this issue by adding a 👍 reaction
  • If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

Per https://aws.amazon.com/blogs/aws/introducing-karpenter-an-open-source-high-performance-kubernetes-cluster-autoscaler/

Before Karpenter, Kubernetes users needed to dynamically adjust the compute capacity of their clusters to support applications using Amazon EC2 Auto Scaling groups and the Kubernetes Cluster Autoscaler. Nearly half of Kubernetes customers on AWS report that configuring cluster auto scaling using the Kubernetes Cluster Autoscaler is challenging and restrictive.

We should look at how doing this with Pulumi as-is looks like and whether there's any opportunities to make it simpler.

Affected area/feature

@t0yv0 t0yv0 added needs-triage Needs attention from the triage team kind/enhancement Improvements or new features labels Apr 3, 2024
@t0yv0
Copy link
Member Author

t0yv0 commented Apr 3, 2024

Related: #371

There's a few more org:pulumi search hits on Karpenter.

@t0yv0
Copy link
Member Author

t0yv0 commented Apr 3, 2024

Courtesy of @jkodroff

@mickdelaney
Copy link

👍🏻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement Improvements or new features size/L Estimated effort to complete (up to 10 days).
Projects
Status: No status
Development

No branches or pull requests

4 participants