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
Update create-external-load-balancer.md #41926
Conversation
describe Healcth check node port response add info about new response header in 1.28 kubernetes/kubernetes#118999 This was discussed on SIG Network on 6th July 2023
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/assign @thockin @danwinship @sftim depends on kubernetes/kubernetes#118999 |
### Caveats and limitations when preserving source IPs | ||
|
||
Health check node port serves HTTP traffic. The response body contains JSON service name, namespace and number |
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 doesn't belong under that heading.
I'm not sure it really belongs in this document at all though; this is information that LoadBalancer implementations need to know. It's not really useful to end users of Kubernetes...
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.
@sftim we want to add this information about the healthceck Nodeport used for Services with type LoadBalancer when externalTrafficPolicy
is set to Local , so implementations can now the nodes with pods and how many pods are running on the node. Since you were restructuring this documentation recently, can you help us to identify the best place to add it?
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.
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.
If it helps, you can frame it as a note along the lines of “Older Kubernetes releases had a shortcoming where …”
/milestone clear |
/close |
@tengqm: 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. |
describe Health check node port response
add info about new response header in 1.28
kubernetes/kubernetes#118999
This was discussed on SIG Network on 6th July 2023