HTTP Forward Proxy Support

    It is assumed the proxy is already existing. If you want a private topology on AWS, for example, with a proxy instead of a NAT instance, you’ll need to create the proxy yourself. See Running in a shared VPC.

    Add spec.egressProxy port and url as follows

    Most clients will blindly try to use the proxy to make all calls, even to localhost and the local subnet, unless configured otherwise. Some basic exclusions necessary for successful launch and operation are added for you at initial cluster creation. If you wish to add additional exclusions, add or edit egressProxy.excludes with a comma separated list of hostnames. Matching is based on suffix, ie, corp.local will match images.corp.local, and will match corp.local and images.corp.local, following typical no_proxy environment variable conventions.

    1. spec:
    3.       host: proxy.corp.local
    4.       port: 3128