Long wait time for Serverless deployments
Hi perhaps someone can help. We've got a various workloads running on Runpod. We deploy to Runpod using SST. Updating the a template with the new image to deploy works great in our CI (github actions). Once we've deployed our updated code to Runpod we want validate that our application is working so we run some tests by invoking the endpoint and asserting on various outputs produced. We do this with preview environments (per pull request) and in a staging environment on the way out to production. We realised a while ago that our tests would often be running against an older version of the code since Runpod handn't had a chance to pull the newer image from Dockerhub.
Our solution to this was to add a Job in the CI that would repeatedly call the
Recently, however, we made a change to set
The problem is that since setting minWorkers to
My questions:
1. How do I know reliably when an endpoint will start processing requests on workers that are running the latest image?
2. Is there a better way to do what I'm doing?
Our solution to this was to add a Job in the CI that would repeatedly call the
/runsyncRecently, however, we made a change to set
minWorkers: 0The problem is that since setting minWorkers to
0My questions:
1. How do I know reliably when an endpoint will start processing requests on workers that are running the latest image?
2. Is there a better way to do what I'm doing?
