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

AWS: Investigate Saving Plans purchases #7074

Closed
ameukam opened this issue Jul 26, 2024 · 7 comments
Closed

AWS: Investigate Saving Plans purchases #7074

ameukam opened this issue Jul 26, 2024 · 7 comments
Labels
area/infra/aws Issues or PRs related to Kubernetes AWS infrastructure lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/backlog Higher priority than priority/awaiting-more-evidence. sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra.
Milestone

Comments

@ameukam
Copy link
Member

ameukam commented Jul 26, 2024

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

@ameukam ameukam added the sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra. label Jul 26, 2024
@k8s-ci-robot k8s-ci-robot added area/infra/aws Issues or PRs related to Kubernetes AWS infrastructure lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/backlog Higher priority than priority/awaiting-more-evidence. labels Jul 26, 2024
@ameukam ameukam added this to the v1.32 milestone Jul 26, 2024
@ameukam
Copy link
Member Author

ameukam commented Jul 26, 2024

cc @xmudrii

@ameukam
Copy link
Member Author

ameukam commented Aug 6, 2024

cc @bryantbiggs @sftim
In case you are interested

@bryantbiggs
Copy link
Contributor

I've pinged a few folks who are knowledgeable in this area (spot, compute savings plans, etc.)

@ameukam
Copy link
Member Author

ameukam commented Aug 6, 2024

@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.

@ameukam
Copy link
Member Author

ameukam commented Nov 21, 2024

I've pinged a few folks who are knowledgeable in this area (spot, compute savings plans, etc.)

Any feedback from your pings ?

@ameukam
Copy link
Member Author

ameukam commented Nov 24, 2024

Feedback from AWS:

Unfortunately AWS Credits cannot be used to purchase Savings Plans. AWS Credits can be applied to many AWS services and pay-as-you-go pricing, but they cannot be used for Savings Plans purchases. Savings Plans require an upfront commitment and must be paid for with actual currency rather than credits.

/close

@k8s-ci-robot
Copy link
Contributor

@ameukam: Closing this issue.

In response to this:

Feedback from AWS:

Unfortunately AWS Credits cannot be used to purchase Savings Plans. AWS Credits can be applied to many AWS services and pay-as-you-go pricing, but they cannot be used for Savings Plans purchases. Savings Plans require an upfront commitment and must be paid for with actual currency rather than credits.

/close

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.

@github-project-automation github-project-automation bot moved this from 📋 Backlog to ✅ Done in AWS Infrastructure (SIG K8s Infra) Nov 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/infra/aws Issues or PRs related to Kubernetes AWS infrastructure lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/backlog Higher priority than priority/awaiting-more-evidence. sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra.
Projects
Status: Done
Development

No branches or pull requests

3 participants