Unfortunately that is the only real answer today, as far as I know. We do not have an egress NAT.
On Thu, Jan 12, 2017 at 2:47 PM, <mariocas...@gmail.com> wrote: > Hi, we have to access some resource that uses an IP whitelist (plus > authentication and SSL) in real time. > > So we need that outgoing traffic from our K8s cluster always has the same IP. > This way we add this IP to the whitelist and we can access the resources. > > I found tons of information about how to set up incoming traffic but almost > nothing for outgoing. > > The only thing I found was to set a Compute Engine instance (that seems like > it can contain a static outgoing IP) to route traffic through but, is it > going to become a single point of failure. > > Any ideas? > > -- > 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. -- 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.
