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.

Sign up for GitHub

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

Jump to bottom

Explore load balancer support on VMC #83

Open
frapposelli opened this issue Oct 10, 2018 · 12 comments
Open

Explore load balancer support on VMC #83

frapposelli opened this issue Oct 10, 2018 · 12 comments
Assignees
@akutz
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Milestone
Next

Comments

@frapposelli
Copy link
Member

vSphere does not come with a load balancer facility out of the box, but when running in VMC (a.k.a. VMware on AWS) we have access to the ELB service provided by AWS.

This issue should track an exploratory effort to scope the feasibility and the work needed to bring support for ELB in cloud-provider-vsphere.

/kind feature
/assign @akutz
@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Oct 10, 2018
@embano1
Copy link
Member

embano1 commented Oct 25, 2018

This exploration could be used to push VCP zones phase 2 implementation forward which is dealing with stretched clusters. We have some thoughts on how to address it, but non of it is ideal as all of the have some drawbacks when it comes to node label drift.

Subscribing here to follow the conversation.

@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 Jan 23, 2019
@sflxn
Copy link

sflxn commented Jan 23, 2019

We're going to need this AND a general solution outside of VMC for cluster api, v1alpha1. If I'm not mistaken, HA support (as implemented in kubeadm) requires a load balancer.

@frapposelli
Copy link
Member Author

/remove-lifecycle stale

@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 Feb 13, 2019
@frapposelli frapposelli added this to the Next milestone Mar 6, 2019
@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 Jun 4, 2019
@smazurov
Copy link

smazurov commented Jun 5, 2019

I really do want to see if this can be addressed as either part of this provider or otherwise.

@frapposelli
Copy link
Member Author

/remove-lifecycle stale

@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 Jun 5, 2019
@frapposelli
Copy link
Member Author

this is going to be important for CAPV.

@frapposelli frapposelli added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. labels Jul 3, 2019
@frapposelli
Copy link
Member Author

explore the possibility of creating a new provider specifically for VMC

@akutz
Copy link
Member

akutz commented Jul 3, 2019 •
edited

I really dislike the idea of a separate provider for this. It should be easy enough to bake into the current one.

@krisdock
Copy link

krisdock commented Aug 1, 2019

we are exploring essential pks on vmc. we'd love to know a timeline for load balancing capability within the vsphere (or vmc) cloud provider.

@frapposelli
Copy link
Member Author

/priority important-longterm

@k8s-ci-robot k8s-ci-robot added the priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. label Sep 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@akutz akutz

Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
None yet
Milestone
Next
Development

No branches or pull requests
8 participants
@smazurov @akutz @frapposelli @sflxn @krisdock @embano1 @k8s-ci-robot @fejta-bot