Skip to content
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 service-cluster-ip-range to controller-manager args #5894

Merged
merged 2 commits into from
Jul 21, 2022

Conversation

brandond
Copy link
Member

Proposed Changes

Add service-cluster-ip-range to controller-manager args.

Also replace getLocalhostIP with Loopback helper method.

note: This does not absolve users from having to manually correct the node-cidr-mask values if they reduce the cluster cidrs below the default sizes. This only addresses the argument being missing from the controller-manager.

Types of Changes

bugfix

Verification

See linked issue

Testing

Linked Issues

User-Facing Change

The configured service CIDR is now passed to the Kubernetes controller-manager via the `--service-cluster-ip-range` flag. Previously this value was only passed to the apiserver.

Further Comments

@brandond brandond requested a review from a team as a code owner July 21, 2022 18:23
Signed-off-by: Brad Davidson <brad.davidson@rancher.com>
@brandond brandond force-pushed the controller_manager_service_cluster branch 2 times, most recently from 2896468 to 848b314 Compare July 21, 2022 21:51
Requires tweaking existing method signature to allow specifying whether or not IPv6 addresses should be return URL-safe.

Signed-off-by: Brad Davidson <brad.davidson@rancher.com>
@brandond
Copy link
Member Author

CI is green other than s390x (down due to hardware issues) and a flake. Merging.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants