You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/blog/_posts/2022-05-23-service-ip-dynamic-and-static-allocation.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,12 +25,12 @@ _statically_
25
25
: you specify an IP address of your choice, from within the configured IP range for Services.
26
26
27
27
Across your whole cluster, every Service `ClusterIP` must be unique.
28
-
Trying to create a Service with a `ClusterIP` that has already
28
+
Trying to create a Service with a specific `ClusterIP` that has already
29
29
been allocated will return an error.
30
30
31
31
## Why do you need to reserve Service Cluster IPs?
32
32
33
-
Because you may want to have Services running in well-known IP addresses, so other components and
33
+
Sometimes you may want to have Services running in well-known IP addresses, so other components and
34
34
users in the cluster can use them.
35
35
36
36
The best example is the DNS Service for the cluster. Some Kubernetes installers assign the 10th address from
@@ -77,7 +77,7 @@ allocation strategy for Services, reducing the risk of collision.
77
77
The `ClusterIP` range will be divided, based on the formula `min(max(16, cidrSize / 16), 256)`,
78
78
described as _never less than 16 or more than 256 with a graduated step between them_.
79
79
80
-
Dynamically IP assignment will use the upper band by default, once this has been exhausted it will
80
+
Dynamic IP assignment will use the upper band by default, once this has been exhausted it will
81
81
use the lower range. This will allow users to use static allocations on the lower band with a low
82
82
risk of collision.
83
83
@@ -132,6 +132,6 @@ pie showData
132
132
133
133
The current SIG-Network [KEPs](https://github.com/orgs/kubernetes/projects/10) and [issues](https://github.com/kubernetes/kubernetes/issues?q=is%3Aopen+is%3Aissue+label%3Asig%2Fnetwork) on GitHub illustrate the SIG’s areas of emphasis.
134
134
135
-
[SIG-Network meetings](https://github.com/kubernetes/community/tree/master/sig-network) are a friendly, welcoming venue for you to connect with the community and share your ideas.
135
+
[SIGNetwork meetings](https://github.com/kubernetes/community/tree/master/sig-network) are a friendly, welcoming venue for you to connect with the community and share your ideas.
0 commit comments