Not sure what you really mean. You use a load balancer that exposes the kubernetes service typically. You can also use an ingress controller.
But why involve, and how, api gateway? And ELB have a security group, you just enable what is reasonable there if you want. Or just use service type load balancer and Kubernetes will do it for you (sg and that). On Sunday, November 26, 2017, <tamir.dres...@gmail.com> wrote: > Hi All, > > I'm new to working with k8s, and I was wondering what do you think is the > best practice when hosting on AWS for exposing your public-facing services? > do you hold your backends and APIs on the same cluster and use AWS API > Gateway to channel the request to the services? do you add another public > subnet where you put your public-facing services on it? do you do both? do > you do anything else? > > Thanks > > -- > You received this message because you are subscribed to the Google Groups > "Kubernetes user discussion and Q&A" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to kubernetes-users+unsubscr...@googlegroups.com <javascript:;>. > To post to this group, send email to kubernetes-users@googlegroups.com > <javascript:;>. > Visit this group at https://groups.google.com/group/kubernetes-users. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and Q&A" group. To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-users+unsubscr...@googlegroups.com. To post to this group, send email to kubernetes-users@googlegroups.com. Visit this group at https://groups.google.com/group/kubernetes-users. For more options, visit https://groups.google.com/d/optout.
