Merge pull request #48531 from network-charles/network-charles-patch-2

Fix Typo in Cluster IP Allocation Page
pull/48543/head
Kubernetes Prow Robot 2024-10-25 02:32:52 +01:00 committed by GitHub
commit 3171c0ba59
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 3 additions and 3 deletions

View File

@ -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}