sparse-intern-71089
01/30/2019, 11:06 PMgentle-diamond-70147
01/31/2019, 12:02 AMchilly-photographer-60932
01/31/2019, 12:47 AMchilly-photographer-60932
01/31/2019, 12:47 AMELB that was spun up part of k8s loadbalancer.chilly-photographer-60932
01/31/2019, 12:47 AMaws cert to that loadbalancer.flat-flag-46972
01/31/2019, 1:31 AMService objectschilly-photographer-60932
01/31/2019, 2:18 AMchilly-photographer-60932
01/31/2019, 2:21 AMchilly-photographer-60932
01/31/2019, 2:22 AMaws cert.white-balloon-205
flat-flag-46972
01/31/2019, 3:52 AMService of type LoadBalancer that creates an ELB automagically. You can throw some annotations on that Service to specify protocol, port, and ACM cert ARN. The ELB is all managed by Kuberneteswhite-balloon-205
flat-flag-46972
01/31/2019, 2:58 PMbreezy-hamburger-69619
01/31/2019, 5:09 PMLoadBalancer typed Service. However, exposing a LB-typed service like this isn’t recommended as you directly put the application out there with no form of ingress management, rate limiting, proxying benefits etc. As an alternative, consider standing up any of the Ingress Controllers offered in the community with a LB of its own, to front your services, as it’ll provide you with host & path based routing management, can terminate SSL/TLS by leveraging k8s Secrets and provides OOTB functionality that your app may not natively have.breezy-hamburger-69619
01/31/2019, 5:13 PM