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

[EKS] [request]: Support EKS Auto components individually #2483

Open
stevehipwell opened this issue Dec 4, 2024 · 4 comments
Open

[EKS] [request]: Support EKS Auto components individually #2483

stevehipwell opened this issue Dec 4, 2024 · 4 comments
Labels
EKS Auto Mode EKS Amazon Elastic Kubernetes Service Proposed Community submitted issue

Comments

@stevehipwell
Copy link

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Tell us about your request
I'd like to be able to use EKS Auto components on their own, specifically in this case the compute management via a managed Karpenter instance (see #1792). Ideally some of the constraints for individual components could be lifted when not running in full "auto" mode.

Which service(s) is this request for?
EKS

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
I want to be able to manage compute via Karpenter without needing to manually run compute as is required today (no I don't want to use Fargate).

Are you currently working around this issue?
Running compute via ASGs.

Additional context
n/a

Attachments
n/a

@stevehipwell stevehipwell added the Proposed Community submitted issue label Dec 4, 2024
@mikestef9 mikestef9 added EKS Amazon Elastic Kubernetes Service EKS Auto Mode labels Dec 4, 2024
@sftim
Copy link

sftim commented Dec 13, 2024

This sounds like you'd like a set of Nodes where Karpenter might or might not run (depending on how you've configured other add-ons), but where those nodes don't specify a network plugin, or run CoreDNS, and might or might not support kube-proxy, and…

I think you may as well run Karpenter on a managed node group. If you're free to choose your own Pod network, there's no guarantee that Karpenter Pods can start. Managed would be hard to deliver.

@sftim
Copy link

sftim commented Dec 13, 2024

I can imagine another option, though: don't run the add-ons as Pods. Karpenter likes to run in a container, but it doesn't have to.

@stevehipwell
Copy link
Author

@sftim that's my point, Karpenter could be run as part of the control plane much like cloud controller manager. There also wouldn't need to be much if any compromises for Karpenter functionality in this mode.

@sftim
Copy link

sftim commented Dec 19, 2024

Relevant detail: (AIUI) EKS Auto Mode doesn't run Karpenter as part of the control plane. It's not a small ask.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
EKS Auto Mode EKS Amazon Elastic Kubernetes Service Proposed Community submitted issue
Projects
None yet
Development

No branches or pull requests

4 participants