Add service-cluster-ip-range flag to kube-apiserver config#910
Closed
kagawish wants to merge 1 commit intokelseyhightower:masterfrom
Closed
Add service-cluster-ip-range flag to kube-apiserver config#910kagawish wants to merge 1 commit intokelseyhightower:masterfrom
kagawish wants to merge 1 commit intokelseyhightower:masterfrom
Conversation
Author
|
Already done here: #879 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I think the
kube-apiserverservice configuration needs to include "--service-cluster-ip-range=10.32.0.0/24" to match the service configuration forkube-controller-manager.Otherwise, the Kubernetes API service gets assigned the "10.0.0.1" ClusterIP by default because this service gets created by
kube-apiserver. This, in turn, causes a problem when trying to curl with the API from inside any pod because the pod CA is configured to only verify 10.32.0.1 and not 10.0.0.1 ca.conf.