Bug 1463691 - [DOCS] Missing note that Egress router does not work on AWS
[DOCS] Missing note that Egress router does not work on AWS
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation (Show other bugs)
Unspecified Unspecified
medium Severity high
: ---
: ---
Assigned To: brice
Meng Bo
Vikram Goyal
Depends On:
  Show dependency treegraph
Reported: 2017-06-21 09:58 EDT by Ryan Howe
Modified: 2017-09-09 01:53 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2017-08-24 21:22:09 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Ryan Howe 2017-06-21 09:58:21 EDT
Document URL: 

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.
Comment 2 Ryan Howe 2017-06-21 10:04:32 EDT
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. 

Comment 3 brice 2017-08-09 21:42:35 EDT
PR submitted:


Asked Dan for more info.
Comment 4 openshift-github-bot 2017-08-14 20:17:06 EDT
Commit pushed to master at https://github.com/openshift/openshift-docs

Merge pull request #4991 from bfallonf/egress_aws

Bug 1463691 Admonition on egress routes for aws

Note You need to log in before you can comment on or make changes to this bug.