From c7ba600025c7a3d9d3380118e35f5115aa0f23cf Mon Sep 17 00:00:00 2001 From: roshandawrani Date: Mon, 29 May 2017 11:52:56 +0530 Subject: [PATCH] Fixed a minor mistake The word "creating" seemed missing. global allocation map should have an entry for an IP address that the service gets while it's created, right? --- docs/concepts/services-networking/service.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/concepts/services-networking/service.md b/docs/concepts/services-networking/service.md index 990795f031..f8c7757e51 100644 --- a/docs/concepts/services-networking/service.md +++ b/docs/concepts/services-networking/service.md @@ -550,7 +550,7 @@ ensure that no two `Services` can collide. We do that by allocating each `Service` its own IP address. To ensure each service receives a unique IP, an internal allocator atomically -updates a global allocation map in etcd prior to each service. The map object +updates a global allocation map in etcd prior to creating each service. The map object must exist in the registry for services to get IPs, otherwise creations will fail with a message indicating an IP could not be allocated. A background controller is responsible for creating that map (to migrate from older versions