From a2cb17e4cf4d7fdb7d84dba575f2e5b1368103f9 Mon Sep 17 00:00:00 2001 From: Guang Ya Liu Date: Mon, 4 Jun 2018 13:00:52 +0800 Subject: [PATCH] Remove quota for service type. (#8882) --- content/en/docs/concepts/services-networking/service.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/concepts/services-networking/service.md b/content/en/docs/concepts/services-networking/service.md index a9fbb84d3e..9a152cd853 100644 --- a/content/en/docs/concepts/services-networking/service.md +++ b/content/en/docs/concepts/services-networking/service.md @@ -400,7 +400,7 @@ The default is `ClusterIP`. ### Type NodePort -If you set the `type` field to `"NodePort"`, the Kubernetes master will +If you set the `type` field to `NodePort`, the Kubernetes master will allocate a port from a flag-configured range (default: 30000-32767), and each Node will proxy that port (the same port number on every Node) into your `Service`. That port will be reported in your `Service`'s `spec.ports[*].nodePort` field. @@ -422,7 +422,7 @@ and `spec.clusterIP:spec.ports[*].port`. (If the `--nodeport-addresses` flag in ### Type LoadBalancer On cloud providers which support external load balancers, setting the `type` -field to `"LoadBalancer"` will provision a load balancer for your `Service`. +field to `LoadBalancer` will provision a load balancer for your `Service`. The actual creation of the load balancer happens asynchronously, and information about the provisioned balancer will be published in the `Service`'s `status.loadBalancer` field. For example: