<p>I'm trying to setup frontend for my two web applications by using ingress controller in local kubernetes cluster. I followed all steps outlined in [1] and detailed instructions in [2]. But so far out of luck. The error I got is the following:</p>

<pre><code>Warning CreatingLoadBalancerFailed Error creating load balancer (will retry): failed to ensure load balancer for service default/frontend: error creating loadbalancer a58617b3f260011e8ad84fa163e0c90a: error creating loadbalancer {a58617b3f260011e8ad84fa163e0c90a
Kubernetes external service a58617b3f260011e8ad84fa163e0c90a 7b4db6f7-3fc1-4c07-a84d-5c15b46e3ac2 &lt;nil&gt; }: Expected HTTP response code [201 202] when accessing [POST https://host.xyz.com:9696/v2.0/lbaas/loadbalancers],
but got 409 instead
{"NeutronError": {"message": "Quota exceeded for resources: ['loadbalancer'].", "type": "OverQuota", "detail": ""}}
</code></pre>

<p>and my service stays in a pending state.</p>

<p>So far I have no idea where to look at to identify the problem and would appreciate any advice.</p>

<p>The manifest yaml file is almost identical to [2], it only lists https interface. But here it is for completeness</p>

<pre><code>apiVersion: extensions/v1beta1
kind: Ingress
metadata:
   name: frontend
   annotations:
     ingress.kub.webernetes.io/rewrite-target: /
spec:
  tls:
  - secretName: ing-secret
  replicas: 1
  template:
    metadata:
      labels:
        k8s-app: nginx-ingress-lb
  containers:
  - args:
    - /nginx-ingress-controller
    - "--default-backend-service=$(POD_NAMESPACE)/default-http-backend"
    - "--default-ssl-certificate=$(POD_NAMESPACE)/ing-secret"
  env:
    - name: POD_NAME
      valueFrom:
        fieldRef:
          fieldPath: metadata.name
    - name: POD_NAMESPACE
      valueFrom:
        fieldRef:
          fieldPath: metadata.namespace
  image: "gcr.io/google_containers/nginx-ingress-controller:0.9.0-beta.5"
  rules:
  - host: host.xxx.com
    https:
      paths:
      - path: /app1
        backend:
          serviceName: app1
          servicePort: 8881
      - path: /app2
        backend:
          serviceName: app2
          servicePort: 8882
---
apiVersion: v1
kind: Service
metadata:
  name: frontend
spec:
  type: LoadBalancer
  ports:
  - name: https
    port: 443
    targetPort: https
  selector:
    k8s-app: nginx-ingress-lb
</code></pre>

<p>[1] <a href="https://kubernetes.io/docs/concepts/services-networking/ingress/" rel="nofollow noreferrer">https://kubernetes.io/docs/concepts/services-networking/ingress/</a></p>

<p>[2] <a href="https://hackernoon.com/setting-up-nginx-ingress-on-kubernetes-2b733d8d2f45" rel="nofollow noreferrer">https://hackernoon.com/setting-up-nginx-ingress-on-kubernetes-2b733d8d2f45</a></p>

<p>It looks like OpenStack lbaas is being used by kubernetes to provision the load balancer service underlying the ingress resource (see <code>https://host.xyz.com:9696/v2.0/lbaas/loadbalancers</code> in the error log)</p>

<p>AFAIK this error indicates a resource limit has been reached on the number of load balancers provisioned. I would raise the issue with your cluster administrator.</p>
