Document URL: https://docs.openshift.com/container-platform/3.5/admin_guide/managing_networking.html#admin-guide-limit-pod-access-egress-router Section Number and Name: Using an Egress Router to Allow External Resources to Recognize Pod Traffic Describe the issue: Currently AWS is in capable of using macvlan, this should be noted in the docs that the egress routers does not work with AWS. Suggestions for improvement: Add note that egress router will not work with AWS.
We should also note what can be used when on AWS as an alternative. I think the following outlines different services that can be used. One of these might work instead of the egress. https://aws.amazon.com/answers/networking/controlling-vpc-egress-traffic/
PR submitted: https://github.com/openshift/openshift-docs/pull/4991 Asked Dan for more info.
Commit pushed to master at https://github.com/openshift/openshift-docs https://github.com/openshift/openshift-docs/commit/59ea413c0a41ab840a6c6e53862323578051c1be Merge pull request #4991 from bfallonf/egress_aws Bug 1463691 Admonition on egress routes for aws
Link to published docs: https://access.redhat.com/documentation/en-us/openshift_container_platform/3.6/html-single/cluster_administration/#admin-guide-limit-pod-access-egress-router