-
Notifications
You must be signed in to change notification settings - Fork 4.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
Add a default ingress ip range #10500
Conversation
Is this correct? I couldn't see how the 'cloud-provider' argument will be populated in config.KubeMasterConfig, so I'm not sure how the check in MasterArgs.BuildSerializeableMasterConfig() will ever fail. |
97a6ede
to
07be0a9
Compare
[test] |
// that will be allocated from. For security reasons, you should | ||
// ensure that this range does not overlap with the CIDRs reserved | ||
// for external ips, nodes, pods, or services. | ||
IngressIPNetworkCIDR string |
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.
You don't need to add this here - we stopped allowing all but "critical" new flags here. Just adding it to the config is sufficient
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.
My intent was to allow an admin to set 0.0.0.0/32 to avoid having the default be set. From what I can tell, if IngressIPNetworkCIDR can't be set by arg, BuildSerializeableMasterConfig will always set the default ingress cidr (unless it conflicts with arg-provided service and cluster net). Am I missing something, or is that what you intend?
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.
a7a3f9c
to
79df588
Compare
If no ingress ip range is specified, default to a private range. Ingress ip allocation can be disabled by specifying "0.0.0.0/32" for the range.
79df588
to
ee401cc
Compare
Evaluated for origin test up to ee401cc |
continuous-integration/openshift-jenkins/test SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/8263/) |
LGTM [merge] |
continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/8263/) (Image: devenv-rhel7_4883) |
Evaluated for origin merge up to ee401cc |
If no ingress ip range is specified, default to a private range.
Ingress ip allocation can be disabled by specifying "0.0.0.0/32" for the range.
Addresses #10387
cc: @smarterclayton