-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
Handle Empty clusterCIDR #36833
Handle Empty clusterCIDR #36833
Conversation
Can a kubernetes member verify that this patch is reasonable to test? If so, please reply with "@k8s-bot ok to test" on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands will still work. Regular contributors should join the org to skip this step.
If you have questions or suggestions related to this bot's behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
|
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.
Didn't you mention that you were writing an e2e for this (iptables-restore --test)? or do you want to send a follow up, or file a bug and we'll add it sometime since it sounds useful to detect a bad configuration and explicitly warn
onlyLocalNodePorts(t, fp, ipt, true) | ||
} | ||
|
||
func onlyLocalNodePorts(t *testing.T, fp *Proxier, ipt *iptablestest.FakeIPTables, shouldLBTOSVCRuleExist bool) { |
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.
can you just check the fp.clusterCIDR and get rid of the last bool arg?
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.
Done.
I will open an issue and handle it there separately. I started it but realized it is more work than I thought. Regards, Mandar U Jog
|
Empty clusterCIDR causes invalid rules generation. Fixes issue kubernetes#36652
6b5347e
to
3fdc343
Compare
LGTM thanks |
@bprashanth Thanks, Tests passed. |
@k8s-bot test this [submit-queue is verifying that this PR is safe to merge] |
Automatic merge from submit-queue |
What this PR does / why we need it:
Handles empty clusterCIDR by skipping the corresponding rule.
Which issue this PR fixes
fixes #36652
Special notes for your reviewer:
Empty clusterCIDR causes invalid rules generation.
Fixes issue #36652
This change is