From e57546d9a1a218b971ef1b19be8376b43db2d9e3 Mon Sep 17 00:00:00 2001 From: Charles Uneze Date: Thu, 24 Oct 2024 17:03:08 +0100 Subject: [PATCH] Update cluster-ip-allocation.md --- .../concepts/services-networking/cluster-ip-allocation.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/en/docs/concepts/services-networking/cluster-ip-allocation.md b/content/en/docs/concepts/services-networking/cluster-ip-allocation.md index 7e54d8253f..54284cec72 100644 --- a/content/en/docs/concepts/services-networking/cluster-ip-allocation.md +++ b/content/en/docs/concepts/services-networking/cluster-ip-allocation.md @@ -69,9 +69,9 @@ spec: type: ClusterIP ``` -but as it was explained before, the IP address 10.96.0.10 has not been reserved; if other Services are created -before or in parallel with dynamic allocation, there is a chance they can allocate this IP, hence, -you will not be able to create the DNS Service because it will fail with a conflict error. +But, as it was explained before, the IP address 10.96.0.10 has not been reserved. +If other Services are created before or in parallel with dynamic allocation, there is a chance they can allocate this IP. +Hence, you will not be able to create the DNS Service because it will fail with a conflict error. ## How can you avoid Service ClusterIP conflicts? {#avoid-ClusterIP-conflict}