-
Notifications
You must be signed in to change notification settings - Fork 824
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
AWS: Investigate Saving Plans purchases #7074
Comments
cc @xmudrii |
cc @bryantbiggs @sftim |
I've pinged a few folks who are knowledgeable in this area (spot, compute savings plans, etc.) |
@bryantbiggs Thank you! I think we have time to have a long conversation (arm64 scheduling, mix nodepools, etc...) about this and ensure we can buy on Jan 2025 or sooner. |
Any feedback from your pings ? |
Feedback from AWS:
/close |
@ameukam: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
we had multiple conversations about this.
We should take a look at saving plans for either AWS Compute in general or specifically EC2 instances family so we can potentially purchase them in early 2025.
Refs:
cc @dims @BenTheElder @upodroid
/milestone v1.32
/area infra
/area infra/aws
/priority backlog
/lifecycle frozen
The text was updated successfully, but these errors were encountered: