Warm Up Nodes Options (Hibernation)
### Tell us about your request Allow Kaprneter to provision more nodes in a hibernated state which would decrease the new nodes provisioning time for rapid scaling. ### Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard? Kaprneter is excellent for optimizing the cluster capacity; however, on the other side, applications that require rapid scaling will need to wait until the new nodes are provisioned. There is a proposal [here](https://github.com/aws/karpenter/issues/3240) to add headroom logic, But that means we are still going to have running nodes with no workloads which they are being charged for. Another option is to support Hibernation (Stopped Instances), which will be bootstrapped and ready to join the clusters once needed. This feature is already supported out of the box as [Warm Pool for Auto Scaling Group](https://docs.aws.amazon.com/autoscaling/ec2/userguide/ec2-auto-scaling-warm-pools.html) ### Are you currently working around this issue? Using Low Priority Pods could be less practical from a cost-saving perspective. Similar to https://github.com/aws/karpenter/issues/3240 ### Additional Context _No response_ ### Attachments _No response_ ### Community Note * Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request * Please do not leave "+1" o
Posted by abebars on Apr 24, 2023, 4:22 AM
Tags
Related issues
- >Beef is already too expensive for most people.
- I gave this a go a couple of years ago.
- I haven't seen any use cases around me, although I'm not that advanced user.
- [BUG] Pro Max 5x Quota Exhausted in 1.5 Hours Despite Moderate Usage
- > Unfortunately it doesn't offer free hosting for hobbyists.
- Still the same HID remapping project from last month (I was hoping to be done by now, but hardware is hard): https://github.co...
Raise real-world problems, find people facing the same issue, and discuss solutions.2,500 issues0 comments
pricing (Software)
>Beef is already too expensive for most people.
I gave this a go a couple of years ago.
I haven't seen any use cases around me, although I'm not that advanced user.
[BUG] Pro Max 5x Quota Exhausted in 1.5 Hours Despite Moderate Usage
> Unfortunately it doesn't offer free hosting for hobbyists.
Still the same HID remapping project from last month (I was hoping to be done by now, but hardware is hard): https://github.co...
This criticism seems like a complete non-sequitur to me.
Bring back the GitHub Copilot in the CLI commands to not break workflows
Warm Up Nodes Options (Hibernation)
### Tell us about your request Allow Kaprneter to provision more nodes in a hibernated state which would decrease the new nodes provisioning time for rapid scaling. ### Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard? Kaprneter is excellent for optimizing the cluster capacity; however, on the other side, applications that require rapid scaling will need to wait until the new nodes are provisioned. There is a proposal [here](https://github.com/aws/karpenter/issues/3240) to add headroom logic, But that means we are still going to have running nodes with no workloads which they are being charged for. Another option is to support Hibernation (Stopped Instances), which will be bootstrapped and ready to join the clusters once needed. This feature is already supported out of the box as [Warm Pool for Auto Scaling Group](https://docs.aws.amazon.com/autoscaling/ec2/userguide/ec2-auto-scaling-warm-pools.html) ### Are you currently working around this issue? Using Low Priority Pods could be less practical from a cost-saving perspective. Similar to https://github.com/aws/karpenter/issues/3240 ### Additional Context _No response_ ### Attachments _No response_ ### Community Note * Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request * Please do not leave "+1" o
Comments (0)
No comments yet. Start the discussion.