How to setup micro gateway behind company firewall?
If micro edge gateway is behind company firewall and want to connect to cloud edge, how to setup proxy parameters to use authenticated HTTP/HTTPS calls from behind firewall. For example to execute following command successfully:
./ edgemicro configure -o <org-name>-e <env-name>-u <your Apigee email>
Hi -- we added more detail to the documentation here:
http://docs.apigee.com/microgateway/content/edge-microgateway-operations
If you search that page for "tunnel" you'll see the note that explains how to configure the proxy using environment variables.
If you like us are trying to use the Edge Microgateway as a service in a K8s cluster the proxy configuration was initially a challenge.
The main issue is that that our proxy is external to the cluster and configuring the proxy with tunnelling meant that requests fail as the proxy cannot reach inside the cluster and we do not want to pass over an ingress controller.
Our target hosts inside the K8s cluster look like this
service-name.namespace:port
As we do not want to exhaustively list all allowed names in the NO_PROXY variable and adding them dynamically requires a redeployment of the Edge Microgateway, the solution we ended up with was to specify
name: "NO_PROXY" value: "*:8080"
... in the environment variable section of the Deployment specification.
Limiting the services to run on a specific port (8080) is an acceptable solution for us.
This said the ideal solution would be to have a dedicated proxy configuration for all Edge requests and leave the general node.js proxy configuration untouched for Edge communication.
Set following environment variable before doing any cli/agent commands and it will get honored.
HTTP_PROXY / http_proxy HTTPS_PROXY / https_proxy
There's been a recent feature and doc update for using HTTP proxy on Edge Micro (v3.1.2). For details, see:
Use an HTTP proxy for communication with Apigee Edge and
Use an HTTP proxy for target communication
