From f04ac5e29c6884b7ade5ef6e75aefedb7ea32a0e Mon Sep 17 00:00:00 2001 From: Noah Huppert Date: Fri, 15 Sep 2017 15:08:30 -0400 Subject: [PATCH] default backend service quota now 5 --- controllers/gce/BETA_LIMITATIONS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/controllers/gce/BETA_LIMITATIONS.md b/controllers/gce/BETA_LIMITATIONS.md index e2d92a3fe..47fdb4978 100644 --- a/controllers/gce/BETA_LIMITATIONS.md +++ b/controllers/gce/BETA_LIMITATIONS.md @@ -24,7 +24,7 @@ Before you can receive traffic through the GCE L7 Loadbalancer Controller you ne ## Quota -GLBC is not aware of your GCE quota. As of this writing users get 3 [GCE Backend Services](https://cloud.google.com/compute/docs/load-balancing/http/backend-service) by default. If you plan on creating Ingresses for multiple Kubernetes Services, remember that each one requires a backend service, and request quota. Should you fail to do so the controller will poll periodically and grab the first free backend service slot it finds. You can view your quota: +GLBC is not aware of your GCE quota. As of this writing users get 5 [GCE Backend Services](https://cloud.google.com/compute/docs/load-balancing/http/backend-service) by default. If you plan on creating Ingresses for multiple Kubernetes Services, remember that each one requires a backend service, and request quota. Should you fail to do so the controller will poll periodically and grab the first free backend service slot it finds. You can view your quota: ```console $ gcloud compute project-info describe --project myproject