Document double nat scenario for OpenStack deployments #806
Conversation
sridhargaddam
requested review from
dfarrell07,
Oats87,
skitt and
tpantelis
as code owners
|
🤖 Created branch: z_pr806/sridhargaddam/issue-805 |
✅ Deploy Preview for elated-bell-2913d9 ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
Fixes: submariner-io#805 Signed-off-by: Sridhar Gaddam <[email protected]>
|
|
||
| In this case case, A & B cluster gateways have direct reachability over their private | ||
| In this case, clusters C & D are neither reachable on their private IPs (192.168.0.4 and 192.168.0.4) nor |
There was a problem hiding this comment.
Shouldn't it be 192.168.128.4 ?
There was a problem hiding this comment.
Why? The diagram uses 192.168.0.4
There was a problem hiding this comment.
Private IPs are the node-ips. As per the diagram its 192.168.0.4 (deliberately shown the same IPs as its possible in such deployments) and the private floating-ips are 10.2.0.1 and 10.2.0.2 respectively. The public-ip auto-discovery for such clusters would be the same for both (2.1.1.1).
There was a problem hiding this comment.
Ooops, I missed the diagram
|
|
||
|  | ||
|
|
||
| ```bash |
There was a problem hiding this comment.
Q : the annotated public IP (e.g: 10.2.0.1) will be used as EP's public IP for all connections (including to clusters C,D) , can you elaborate how the connection from cluster A to C will work ?
There was a problem hiding this comment.
There is no Cluster A in this topology. Please look at the next scenario and it is currently not supported in Submariner.
|
🤖 Closed branches: [z_pr806/sridhargaddam/issue-805] |
Fixes: #805
Signed-off-by: Sridhar Gaddam [email protected]