Managing savings plan using graphql API
Hi Runpod teams!
I'm currently using multiple GPU pods in secure cloud and planning to utilize savings plan.
We automate provisioning pods using graphql API and trying to integrate savings plan with this system.
We frequently update model server running on runpod and our system handle this upgrade via delete and recreating new pod with new docker parameters.
So my question is if pods with savings plan is deleted, does that plan applied to another pod? For example, if I have pod A with savings plan, then delete A and create new pod B, does that savings plan automatically attach to B, or is there any graphql API that we attach existing savings plan to new or existing other pods?
Also, if I have two pod A with savings plan and B without savings plan, when I delete pod A, does that savings plan automatically transfer to pod B?
5 Replies
I believe it carries over to a new pod but only of the same GPU type.
Savings plans | RunPod Documentation
Cost savings for Your RunPod deployments.
Thanks for fast response!
Does it automatically transfer to another pod in following situation?
"Also, if I have two pod A with savings plan and B without savings plan, when I delete pod A, does that savings plan automatically transfer to pod B?"
No, I think it only carries over when you deploy a new pod, not to an existing pod.
"When you stop a Pod, the Savings Plan associated with it applies to your next deployment of the same card. This means you continue to benefit from your savings commitment even after temporary pauses in your pod usage."
It seems like savings plan only applied when pod A is stopped and then resumed. Does it applied when I completely terminate(remove) pod A and create another pod with same GPU types? I'm quiite confused about what "card" means