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

Create new flag to specify apiserver address for kube-proxy #609

Closed
discordianfish opened this issue Dec 21, 2017 · 5 comments
Closed

Create new flag to specify apiserver address for kube-proxy #609

discordianfish opened this issue Dec 21, 2017 · 5 comments
Assignees
Labels
area/HA kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone

Comments

@discordianfish
Copy link

Right now kubeadm uses the host IP it's running on for the apiserver address in the kube-proxy configmap.
For a multi-master setup where the apiserver are behind a load balancer, we need a way to configure kube-proxy to talk to the load balancer instead.
Therefor I propose adding a flag to kubeadm to set the apiserver address in the kube-proxy config map.

This is probably required for #261
Related:

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 21, 2018
@discordianfish
Copy link
Author

/remove-lifecycle stale
/lifecycle freeze

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 23, 2018
@timothysc timothysc added the kind/feature Categorizes issue or PR as related to a new feature. label Apr 7, 2018
@timothysc
Copy link
Member

/assign @timothysc @fabriziopandini

@timothysc timothysc added area/HA priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Apr 7, 2018
@timothysc timothysc added this to the v1.11 milestone Apr 7, 2018
@fabriziopandini
Copy link
Member

@discordianfish considering the availability of the new API.ControlPlaneEndpoint config option (that could be used also for defining the address of the LB in an HA scenario), is the new flag still needed or not?

@discordianfish
Copy link
Author

Oh right, this can be closed now too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/HA kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Development

No branches or pull requests

5 participants