Open frapposelli opened 6 years ago
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.
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
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.
/remove-lifecycle stale
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
I really do want to see if this can be addressed as either part of this provider or otherwise.
/remove-lifecycle stale
this is going to be important for CAPV.
explore the possibility of creating a new provider specifically for VMC
I really dislike the idea of a separate provider for this. It should be easy enough to bake into the current one.
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.
/priority important-longterm
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