<p>My question is regarding quotas of Google Kubernetes Engine.</p>

<p>I have an instance running 4 pods, each pod is referring to a microservice (api) containing 3 containers:</p>

<ul>
<li>Spring Boot App</li>
<li>esp: endpoints</li>
<li>cloudsqlproxy</li>
</ul>

<p>For each pod (microservice), I have a deployment yaml which includes a nodeport service. Along with that, there is an ingress mapping all these services. Now
I need to deploy another microservice (pod with same 3 containers), but the quota of 5 backend services is in the limit.</p>

<p>I dont know if I'm doing something wrong or this quota is very small. I think, four microservices is very little for a technology that supports this approach.</p>

<p>So, Am I missing something in this architecture / configuration? Something that I'm doing wrong?</p>

<p>Here is my Ingress configuration:</p>

<pre><code>apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: sigma-ingress
  annotations:
    # type of controller to use:
    kubernetes.io/ingress.class: "gce"
    # CORS
    ingress.kubernetes.io/enable-cors: "true"
    #
    # ingress.kubernetes.io/rewrite-target: /
    # Don't rediret to HTTPS
    ingress.kubernetes.io/ssl-redirect: "false"
    # Block HTTP requests
    kubernetes.io/ingress.allow-http: "false"
spec:
  tls:
  - secretName: sigma-ssl
  rules:
  - http:
      paths:
      - path: /agro/*
        backend:
          serviceName: api-agro
          servicePort: 443
      - path: /fazendas
        backend:
          serviceName: api-fazenda
          servicePort: 443
      - path: /fazendas/*
        backend:
          serviceName: api-fazenda
          servicePort: 443
      - path: /clima
        backend:
          serviceName: api-clima
          servicePort: 443
      - path: /clima/*
        backend:
          serviceName: api-clima
          servicePort: 443
      - path: /ocorrencias
        backend:
          serviceName: api-inspecao
          servicePort: 443
      - path: /ocorrencias/*
        backend:
          serviceName: api-inspecao
          servicePort: 443
</code></pre>

<p>Thanks in advance</p>

<p>Peter</p>

Peter Pennings
<p>You are probably hitting the <a href="https://cloud.google.com/load-balancing/docs/backend-service" rel="nofollow noreferrer">GCP Load balancer backend</a> limit which is usually low (mine is 9) This if you several other load balancers with configured backends that are making you hit that limit and you are mentioning that you already have other NodePort services (are they using another load balancer with a different backend?)</p>

<p>Your ingress should use just one backend that points to all the nodes in your cluster.</p>

<p>Besides the gcloud command line, you can see the limit from the UI.</p>

<p><a href="https://i.stack.imgur.com/S3PMs.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/S3PMs.png" alt="backend limit"></a></p>

<p>You can also see the details on the load balancer that is serving your Ingress.</p>

<p><a href="https://i.stack.imgur.com/MLPmH.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/MLPmH.png" alt="backend"></a></p>

<p>And you can see all your load balancer too:</p>

<p><a href="https://i.stack.imgur.com/1vUNy.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/1vUNy.png" alt="lbs"></a></p>

<p>You can <a href="https://cloud.google.com/compute/quotas#requesting_additional_quota" rel="nofollow noreferrer">request a backend quota increase</a> from GCP, or you can remove unused load balancers.</p>
