4 ms·

Status page is inaccurate as issues doesn't only affect the web UI, the same operations are not functioning via the CLI.

camhutch 8y ago
I just tried turning up my 1-node test cluster via terraform, and it worked fine. I would have thought the gcloud CLI would be using the same API. I did this in the australia-southeast1-a zone.
base698 8y ago
What operations? Status just shows node pool creation.
- rlancer 8y ago
  Can not create a new Clusters or Node Pool and can not resize exiting Node Pools, as far as users are reporting it's happening in all regions too. Error message when creating a new Cluster: Deploy error: Not all instances running in IGM after 35m7.509000994s. Expect 1. Current errors: [ZONE_RESOURCE_POOL_EXHAUSTED]: Instance 'gke-cluster-3-pool-1-41b0abf8-73d7' creation failed: The zone 'projects/url-shortner-218503/zones/us-west2-b' does not have enough resources available to fulfill the request. Try a different zone, or try again later. - ; .
  - dweekly 8y ago
    Hi, just curious: why are you in us-west2?
    - rlancer 8y ago
      Just the latest region I tried, been trying to spin up Clusters around the country all day.
pm90 8y ago
Its kinda strange that HN seems to be the most effective way to give feedback to Google Cloud :/
- breakingcups 8y ago
  Most transparent, at least.
- Draiken 8y ago
  I also find it weird that on HN where normally people are very skeptical of any argument without data backing it, when it comes to this outage, people are assuming everything written here affects everyone. Perhaps some of the issues are localized? Perhaps it's even user error (it happens, you know?). But because a small amount of HN users say "it's everywhere!" then suddenly people reach for their pitchforks. Sometimes we just don't have all the information.
kenan_warren 8y ago
Yeah almost all regions and zones for any compute instance have been exhausted since about 1pm PST on Friday. I finally got one up last night on us-east1, but my older cluster is basically SOL until it's fixed on us-west1. It went down for an upgrade and never came back up because of the same resource issue.

camhutch 8y ago

I just tried turning up my 1-node test cluster via terraform, and it worked fine. I would have thought the gcloud CLI would be using the same API. I did this in the australia-southeast1-a zone.

base698 8y ago

What operations? Status just shows node pool creation.

rlancer 8y ago
Can not create a new Clusters or Node Pool and can not resize exiting Node Pools, as far as users are reporting it's happening in all regions too. Error message when creating a new Cluster: Deploy error: Not all instances running in IGM after 35m7.509000994s. Expect 1. Current errors: [ZONE_RESOURCE_POOL_EXHAUSTED]: Instance 'gke-cluster-3-pool-1-41b0abf8-73d7' creation failed: The zone 'projects/url-shortner-218503/zones/us-west2-b' does not have enough resources available to fulfill the request. Try a different zone, or try again later. - ; .
- dweekly 8y ago
  Hi, just curious: why are you in us-west2?
  - rlancer 8y ago
    Just the latest region I tried, been trying to spin up Clusters around the country all day.

pm90 8y ago

Its kinda strange that HN seems to be the most effective way to give feedback to Google Cloud :/

breakingcups 8y ago
Most transparent, at least.
Draiken 8y ago
I also find it weird that on HN where normally people are very skeptical of any argument without data backing it, when it comes to this outage, people are assuming everything written here affects everyone. Perhaps some of the issues are localized? Perhaps it's even user error (it happens, you know?). But because a small amount of HN users say "it's everywhere!" then suddenly people reach for their pitchforks. Sometimes we just don't have all the information.

kenan_warren 8y ago

Yeah almost all regions and zones for any compute instance have been exhausted since about 1pm PST on Friday. I finally got one up last night on us-east1, but my older cluster is basically SOL until it's fixed on us-west1. It went down for an upgrade and never came back up because of the same resource issue.