In some rare occasions, some zones might not have enough resources available to fullfill a request. This is done to ensure that there are enough resources in each zone, to ensure that already installed users have enough of them to keep running their applications.
This type of issues are immediately noticed, and currently this is being investigated. For the moment, you can try to do one the following points:
Keep trying to do the deployment until the zone has enough resources.
Relax the requirements of the instance you are creating ( i.e. less CPU/Disk/Memory...)
Try to deploy to another zone within the same region, for example deploy to us-central1-a
. You can see the full list of available zones/regions in this documentation
I would recommend you to go for the third option, as you will be able to create the instances immediately, with the resources you need, and you probably won't be affected by the zone change.