From d8861f9a4ba5f1b9ee9b5435d971cbea3feab8e5 Mon Sep 17 00:00:00 2001 From: Alfonso Palacios Date: Wed, 18 Jul 2018 20:48:19 +0200 Subject: [PATCH] Update service.md (#9562) I think the writer means "reuse" here instead of "replace". Since the idea behind choosing your own IP is to avoid having to make any changes to the DNS. --- content/en/docs/concepts/services-networking/service.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/services-networking/service.md b/content/en/docs/concepts/services-networking/service.md index a88c0261e8..def07b6dd9 100644 --- a/content/en/docs/concepts/services-networking/service.md +++ b/content/en/docs/concepts/services-networking/service.md @@ -273,7 +273,7 @@ Note that the port names must only contain lowercase alphanumeric characters and You can specify your own cluster IP address as part of a `Service` creation request. To do this, set the `.spec.clusterIP` field. For example, if you -already have an existing DNS entry that you wish to replace, or legacy systems +already have an existing DNS entry that you wish to reuse, or legacy systems that are configured for a specific IP address and difficult to re-configure. The IP address that a user chooses must be a valid IP address and within the `service-cluster-ip-range` CIDR range that is specified by flag to the API