-
Notifications
You must be signed in to change notification settings - Fork 14.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
graduate ServiceIPStaticSubrange to GA #37432
Conversation
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site settings. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
/lgtm
/approve
Please target this change to the dev-1.26 branch @aojea /hold |
56cd998
to
7fa9682
Compare
👷 Deploy Preview for kubernetes-io-vnext-staging processing.
|
7fa9682
to
6336cb9
Compare
@sftim updated the PR against 1.26 |
/unhold
|
What I don't get from these docs is: can you have more than 256 Services in your cluster? It's not obvious how the whole available range eventually gets used. |
ups, no, the number of Services is not modified here, this makes a virtual division to not allocate dynamic addresses from this lower range, the blog explains it in more detail https://kubernetes.io/blog/2022/05/23/service-ip-dynamic-and-static-allocation/ |
I'd like to be able to work out the way it works just from the docs - and I want that for readers in general too. For GA, we prefer to have docs that readers can understand without also following links to the KEP, post-release writeup, etc. |
It's OK to copy from that blog article, as much as we'd like to. It's also reasonable to change that blog article to be evergreen: written so that the text doesn't turn stale, and marked as such. Only some minor tweaks would be needed there, and then we can link to it to provide the background detail (we can actually shorten the concept page if we do that). |
ack, let me work on this |
content/en/docs/reference/command-line-tools-reference/feature-gates.md
Outdated
Show resolved
Hide resolved
content/en/docs/reference/command-line-tools-reference/feature-gates.md
Outdated
Show resolved
Hide resolved
b620995
to
6f7421b
Compare
@sftim I've tried to follow your suggestions but I need you to review because I'm not sure if that is what you meant |
ping @sftim |
#### Service IP CIDR block: 10.96.0.0/24 | ||
|
||
Range Size: 2<sup>8</sup> - 2 = 254 | ||
Band Offset: `min(max(16, 256/16), 256)` = `min(16, 256)` = 16 | ||
Static band start: 10.96.0.1 | ||
Static band end: 10.96.0.16 | ||
Range end: 10.96.0.254 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Two problems here:
- We usually don't have H4 for headings, and in this context, we are skipping H3?
- The text lines above would be converted into a single text graph, difficult to read.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Em... interesting that the lines above are not merged by Hugo.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I copied from the blog article, but open to suggestions since I'm not very deep in docs/text format
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Em... interesting that the lines above are not merged by Hugo.
The inline HTML might prevent that. Not sure.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks
Here's some feedback
content/en/docs/concepts/services-networking/cluster-ip-allocation.md
Outdated
Show resolved
Hide resolved
reviewers: | ||
- sftim | ||
- thockin | ||
title: Service ClusterIP allocation |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it a ClusterIP
, or just a virtual cluster IP? I'm not sure on the need for writing this text monospace. Bear in mind that the Service that gets one of these virtual IP addresses might not have the type
field set to "ClusterIP"
. For example, it could be a Service of type: LoadBalancer
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is ClusterIP specific, the LoadBalancer IP is assigned by an external controller and not explained here ... all Services types have a ClusterIP except, headless that use ClusterIP: None
or those with type ExternalName
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
all Services type have a ClusterIP
Right, that's the bit where I'm worried we're confusing readers. In Kubernetes, most Services have a thing, but should we call the thing a ClusterIP
? To me ClusterIP
is a particular enum value. We wouldn't, for example, write:
“the packets are rewritten as they pass through the LoadBalancer
”, even though LoadBalancer
is the type of Service involved there.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see your point, let me summon @danwinship and @thockin they are good expressing these concepts
content/en/docs/concepts/services-networking/cluster-ip-allocation.md
Outdated
Show resolved
Hide resolved
content/en/docs/concepts/services-networking/cluster-ip-allocation.md
Outdated
Show resolved
Hide resolved
content/en/docs/concepts/services-networking/cluster-ip-allocation.md
Outdated
Show resolved
Hide resolved
content/en/docs/concepts/services-networking/cluster-ip-allocation.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Tim Bannister <tim@scalefactory.com>
If the rest of the page is technically accurate, let's ship. Would be nice to see if we can tidy further before the release. /approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sftim, thockin The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/lgtm |
LGTM label has been added. Git tree hash: ca5219a653d552f4fb5d3d2bce1cf3c150d9deaf
|
/lgtm |
The ServiceIPStaticSubrange feature gate, that allows to change the IP allocation algorithm used for Service.ClusterIPs, is graduating to GA.