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
KEP-3836 documentation for 1.30 #45290
KEP-3836 documentation for 1.30 #45290
Conversation
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
Hi @alexanderConstantinescu 👋 just a reminder to take a look at Documenting for a release - PR Ready for Review to get your PR ready for review before Tuesday March 12th 2024 18:00 PST. Thank you! |
62b2878
to
c73cc55
Compare
c73cc55
to
8867c0e
Compare
OK, I've added a section under https://kubernetes.io/docs/concepts/services-networking/service/#loadbalancer which details the readiness / liveness logic around Kube-proxy and terminating/deleting nodes. From the enhancement we had agreed that we wanted to cover pitfalls w.r.t configuring health check for services of I am not fully sure about the wording to use when providing recommendations to service proxy's / cloud providers, but we can refine this later on. I wanted to get this up today for the "ready for review" deadline /cc @thockin |
8867c0e
to
1f0b058
Compare
/sig network Hello @alexanderConstantinescu 👋, thanks for getting this up for review! A friendly reminder of timeline, this PR needs doc review complete by Doc Freeze on March 26th 18:00 PT to get this into the release. @thockin @danwinship @aojea @chanieljdan Please give this a review also - I think your perspective in this domain would be valuable. I appreciate everyone's help and so will our users! Thank you greatly. |
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.
I wonder whether all of this content would find a better home within
https://kubernetes.io/docs/reference/networking/; the Service concept page can have a two sentence summary and a link to the specifics.
How about doing that?
Also, it's kube-proxy
(no capital K); this matches the container images we build.
Does https://kubernetes.io/docs/reference/networking/ports-and-protocols/ need an update for the changes in this KEP? |
Hi @alexanderConstantinescu 👋 I'm reaching out from the Docs team. Just checking in as we approach Docs Freeze on Tuesday March 26th 18:00 PDT. This documentation appears to still be under review. To meet the Docs Freeze, this PR must have a technical review as well as lgtm and approve labels applied, without any unaddressed comments or concerns from SIG Docs. @thockin @danwinship @aojea |
Any thoughts specifically on #45290 (comment)? |
1f0b058
to
d48de51
Compare
No objection from me, I added an additional commit which addresses that: approvers can decide on if we should keep or not |
06f4e09
to
54fcb75
Compare
@@ -488,6 +488,63 @@ route to ready node-local endpoints. If the traffic policy is `Local` and there | |||
are no node-local endpoints, the kube-proxy does not forward any traffic for the | |||
relevant Service. | |||
|
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 wonder if this mostly belongs under the heading ### Traffic to terminating endpoints
. (my guess is: yes it does; you could leave in a one sentence hyperlink to the moved text)
and somewhere you ought to add:
{{< feature-state feature_gate_name="KubeProxyDrainingTerminatingNodes" >}}
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 wonder if this mostly belongs under the heading ### Traffic to terminating endpoints
Not quite, what I've added deals with "traffic to terminating nodes"
and somewhere you ought to add:
What does that do? The feature is beta in 1.30 so enabled by default.
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.
The feature state shortcode tells people they need a particular Kubernetes version to use it - see https://kubernetes.io/docs/contribute/new-content/new-features/#ready-for-review-feature-gates
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.
LGTM on tech review
54fcb75
to
26825ea
Compare
/lgtm |
LGTM label has been added. Git tree hash: 17d0b83e23b65769bb072dec4c77283beb0fb3b6
|
Looks like we're just missing @kubernetes/sig-docs-en-owners Are there any outstanding concerns or is this ready to approve? |
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.
@alexanderConstantinescu Perhaps we should consider setting the dev-1.30
branch as the target branch rather than the main
branch for this pull request. Since the change is related to the feature targeting beta in 1.30.
Also, the PR is currently lacking the doc change to transition the feature gate KubeProxyDrainingTerminatingNodes
from Alpha to Beta. The necessary change should be made in the feature gate description file - kube-proxy-draining-terminating-nodes.md
(here).
Please refer to the documentation here for further information.
Sure, I will open an additional PR and target dev-1.30 then, you can decide on which PR to merge. |
26825ea
to
1ce0f75
Compare
New changes are detected. LGTM label has been removed. |
Opened #45678 - feel free to close this one if needed. |
1ce0f75
to
c94d2eb
Compare
@alexanderConstantinescu If you could kindly update the Enhancements Issue kubernetes/enhancements#3836 with the merged PR number targeting |
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.
Closing this PR as these changes having been merged in dev-1.30
as part of another PR #45678
/close
@dipesh-rawat: Closed this PR. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/milestone 1.30 |
Enhancement: kubernetes/enhancements#3836
Original implementation PR: kubernetes/kubernetes#116470