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?
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?
