Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
support of AWS ELB in kubeapi-load-balancer #183
Comments
|
Juju currently doesn't have any awareness of the AWS ELB proxy resource. There has been talk off/on about this previously. I think tapping someone like @marcoceppi on this one would be good, and he can address accordingly. |
chuckbutler
added
kind/feature
area/kube-api-loadbalancer
labels
Jan 9, 2017
|
-- edit -- (i misunderstood the original request and instead was thinking about the ingress controller, not the apilb) To properly support this we would need an ELB charm to represent that load balancer service, and subsequently, model any additional cloud-specific load balancers for non aws substrate deployments. I'm not certain that's something we would target at this time, but it seems like a good low priority wishlist item or community contribution. When we model features in charms/bundles we tend to consider the full spectrum of deployments from bare-metal first all the way up the abstracted providers list. |
rimusz commentedJan 9, 2017
•
Edited 1 time
-
rimusz
Jan 10, 2017
on AWS it makes more sense to use ELB instead of dedicated VM for
kubeapi-load-balancerusing there
m3.mediuminstance balancer comes at the high price and with no HA :)