support of AWS ELB in kubeapi-load-balancer #183

Open
rimusz opened this Issue Jan 9, 2017 · 2 comments

Comments

2 participants

rimusz commented Jan 9, 2017

on AWS it makes more sense to use ELB instead of dedicated VM for kubeapi-load-balancer
using there m3.medium instance balancer comes at the high price and with no HA :)

Collaborator

chuckbutler commented Jan 9, 2017

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.

Collaborator

chuckbutler commented Jun 21, 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.

@wwwtyro wwwtyro added this to Feature Request in CDK Jan 10, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment