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
Address remaining TODOs in kube-proxy. #46201
Address remaining TODOs in kube-proxy. #46201
Conversation
@k8s-bot unit test this |
// to apply. | ||
return true | ||
} | ||
return len(ecm.items) > 0 |
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 guess this works. I was thinking of the return as "did this update() cause a change", but this should be behaviorally equivalent at the end.
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: thockin, wojtek-t
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
@wojtek-t: The following test(s) failed:
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. I understand the commands that are listed here. |
Automatic merge from submit-queue |
PR 46201 (kubernetes/kubernetes#46201) and others recently have changed the log level at which the complete iptables rules are printed out. They were at log level 3, and Kubernetes now logs them at 5. This brings us in sync with that.
PR 46201 (kubernetes/kubernetes#46201) and others recently have changed the log level at which the complete iptables rules are printed out. They were at log level 3, and Kubernetes now logs them at 5. This brings us in sync with that. Fixes bug 14359 (openshift#14359)
PR 46201 (kubernetes/kubernetes#46201) and others recently have changed the log level at which the complete iptables rules are printed out. They were at log level 3, and Kubernetes now logs them at 5. This brings us in sync with that. Fixes bug 1455655 (https://bugzilla.redhat.com/show_bug.cgi?id=1455655)
PR 46201 (kubernetes#46201) and others recently have changed the log level at which the complete iptables rules are printed out. They were at log level 3, and Kubernetes now logs them at 5. This brings us in sync with that. Fixes bug 1455655 (https://bugzilla.redhat.com/show_bug.cgi?id=1455655) :100644 100644 fc00c52003... c7da6fe180... M pkg/proxy/iptables/proxier.go
PR 46201 (kubernetes#46201) and others recently have changed the log level at which the complete iptables rules are printed out. They were at log level 3, and Kubernetes now logs them at 5. This brings us in sync with that. Fixes bug 1455655 (https://bugzilla.redhat.com/show_bug.cgi?id=1455655) :100644 100644 fc00c52003... c7da6fe180... M pkg/proxy/iptables/proxier.go
Followup PR from the previous two.