Unable to allocate resource on specific zone for Autopilot cluster

[ShiriNmi1520]

Greetings:

I'm trying to deploy a deployment to my Autopilot GKE cluster in the region asia-east1.

However, my deployment didn't start as expected. Instead, I got this log from my cluster.

The zone 'projects/my-project-id/zones/asia-east1-b' does not have enough resources available to fulfill the request.

It looks like a specific zone is in high demand, so I scrambled to find an official document that explains how to configure pod deployment to that zone.

I modified my deployment to the following.

apiVersion: apps/v1
kind: Deployment
metadata:
  name: my-deployment
  namespace: my-namespace
spec:
  replicas: 1
  selector:
    matchLabels:
      app: my-app
  template:
    metadata:
      labels:
        app: my-app
    spec:
      affinity:
        nodeAffinity:
          requiredDuringSchedulingIgnoredDuringExecution:
            nodeSelectorTerms:
            - matchExpressions:
              - key: topology.kubernetes.io/zone
                operator: In
                values:
                - asia-east1-c
                - asia-east1-a
      containers:
        ...Bunch of containers
      volumes:
        ...Bunch of volumes with PVC

Unfortunately, this modification does not work for the Autopilot cluster since I observed the cluster log and can't find any further logs related to the 'Scale-up instance group' event.

Is there any workaround at this time besides creating a new cluster in the other region or waiting for the zone to have enough resources to handle my request?

[Manish_B]

Hello @ShiriNmi1520,

Thank you for contacting Google Cloud Community.

First, our apologies that the Google Cloud resources you need are not currently available. Our goal is to make sure that there are resources in all zones. We take this responsibility very seriously and are working hard to make resources available as soon as possible. We recommend deploying and balancing your workload across multiple zones and regions to reduce the likelihood of an outage and have access to multiple resource pools when you need to expand quickly. Please review our documentation which outlines How to Build Resilient and Scalable Architectures on Google Cloud Platform.

Please note that you are currently using Google Cloud on-demand consumption model which does not provide an assurance in obtaining capacity. We now offer a feature called reservations that provides a very high level of assurance in obtaining capacity on the Google Cloud platform, please see our documentation for details on How to Use this Feature.

Additionally, you could refer to this Google Cloud Service Health Dashboard to know more about the status information on the services that are part of Google Cloud.

Again, we want to offer our sincerest apologies. We are working hard to increase our capacity and make this an exceptionally rare event.

Thanks & Regards,
Manish Bavireddy.  

[garisingh]

Can you post your pod log(s) / events?   Or maybe the output of

kubectl describe pod $POD_NAME

?