OpenShift (the kubernetes++ platform from Red Hat) has an outgoing egress
NAT proxy that works for some people.
https://docs.openshift.com/container-platform/3.5/admin_guide/managing_networking.html#admin-guide-limit-pod-access-egress-router
describes what we built. It works on any cloud or on ba
GKE / Google Cloud in this regard. I can't say for sure what other
clouds offer.
It should be possible to run an HTTP Proxy or other app-specific
proxy, which can get you a long way towards this.
On Mon, May 8, 2017 at 12:14 PM, wrote:
> On Friday, 13 January 2017 02:25:20 UTC+1, Tim Hockin w
On Friday, 13 January 2017 02:25:20 UTC+1, Tim Hockin wrote:
> Unfortunately that is the only real answer today, as far as I know.
> We do not have an egress NAT.
HI Tim, do you speak for GKE or fur kubernetes in general?
--
You received this message because you are subscribed to the Google Gr
Thank you for confirming. I understand the complexity involved on K8s
development but I was hoping for a good fix.
Thank you again
--
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 re
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, 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 K
