-
Notifications
You must be signed in to change notification settings - Fork 39.9k
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
Field status.hostIPs
added for Pod
#109616
Conversation
Please note that we're already in Test Freeze for the |
6483ef2
to
9f8c843
Compare
Types conversion Add dropDisabledStatusFields Add HostIPs by Kubelet I think the reason why the original load is too large is that, it should be that when Feature is disabled, the Conversion section fills HostIPs and then discards in DropDisableDStatusfields. I guess it is enough to fill Hostips by Kubelet when enabling features. |
9f8c843
to
616340b
Compare
is there a specific delta that shows the differences between this PR and the original? are there added tests that would have caught the issues with the previous PR? |
aa3aa91
to
3e2a1a7
Compare
Hi, @thockin |
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
LGTM label has been added. Git tree hash: f5201924c056fd954a946b49696edd91cfbbccbe
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: thockin, wzshiming 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 |
Thanks |
No performance regression this time. 🎉 |
What type of PR is this?
/kind feature
/sig node
/sig network
What this PR does / why we need it:
kubernetes/enhancements#2661
If the Pod runs on an enabled IPv6 dual stack node, hope to get the IPv6 address of node
Which issue(s) this PR fixes:
Original PR #101566
Fixes #101565
Fixes #85443
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: