Hi community - I'm getting a new error , which is very strange; see below. On VSC/GoogleCloudRun , how/why/where do I need to set maxScale..? I notice, now that I do not even have a package.json file (which i see other people sometimes referring to). Everything has been fine for some time.. and now this. Hmm.
-----
Solved! Go to Solution.
> is there some setting there that affects the max instances?
Unfortunately, I don't know.
> The docs say that 100 is the default for maxScale
It's possible that 100 is the max (all things being equal) but that the value is dependent on the value of the CPU (i.e. only certain combinations are allowed). That seems to be the thrust of the error message. It's also possible that wasn't the case previously but that the change is a recent one. Google typically document these changes in the release notes but I don't think it's common for folks to automatically read a release note - people typically only go to it when they hit a snag 🙂
Don't know how to do this from commandline or console but see if you can do it from the UI.
Image 1 - Number of CPUS
Image 2 - Cloud Run Scale
Thank you. Creating a new revision on the Console allowed me access to the maxScale field which I set down to 10, a subsequent Deploy_to_cloud (from Visual Studio Code) worked and pushed my revisions to the endpoint. Thank you. 👍 The docs say that 100 is the default for maxScale, though, and I'm confused as to why I was 'suddenly' forced to crank it back to 10. Of note - I recently changed the Billing account on this cloud project to use a co-owner's Billing Account, and as far as we can tell that billing account is in good standing and ready to go (is there some setting there that affects the maxinstances?)
> is there some setting there that affects the max instances?
Unfortunately, I don't know.
> The docs say that 100 is the default for maxScale
It's possible that 100 is the max (all things being equal) but that the value is dependent on the value of the CPU (i.e. only certain combinations are allowed). That seems to be the thrust of the error message. It's also possible that wasn't the case previously but that the change is a recent one. Google typically document these changes in the release notes but I don't think it's common for folks to automatically read a release note - people typically only go to it when they hit a snag 🙂