Fixes to F5 blueprint docs (#1886)
Co-authored-by: Luca Prete <lucaprete@google.com>
This commit is contained in:
parent
98accdb3ad
commit
bb58469292
|
@ -12,6 +12,6 @@ The blueprints in this folder show how to deploy both private and public active/
|
||||||
|
|
||||||
### F5 BigIP-HA deployment
|
### F5 BigIP-HA deployment
|
||||||
|
|
||||||
<a href="./f5-bigip-ha-active/" title="F5 BigIP HA active-active"><img src="./f5-bigip-ha-active/diagram.png" align="left" width="320px"></a> <p style="margin-left: 340px">The blueprint demonstrates how to deploy active-active F5 BigIP load balancers in a VPC, leveraging the [f5-big-ha-active blueprint](./f5-bigip-ha-active/README.md). In this example, the load balancer is exposed to internal sample clients only and it can handle both IPv4 and an IPv6 traffic.</p>
|
<a href="./f5-bigip-ha-active-deployment/" title="F5 BigIP HA active-active deployment"><img src="./f5-bigip-ha-active-deployment/diagram.png" align="left" width="320px"></a> <p style="margin-left: 340px">The blueprint demonstrates how to deploy active-active F5 BigIP load balancers in a VPC, leveraging the [f5-big-ha-active blueprint](./f5-bigip-ha-active/README.md). In this example, the load balancer is exposed to internal sample clients only and it can handle both IPv4 and an IPv6 traffic.</p>
|
||||||
|
|
||||||
<br clear="left">
|
<br clear="left">
|
||||||
|
|
Binary file not shown.
Before Width: | Height: | Size: 63 KiB After Width: | Height: | Size: 63 KiB |
File diff suppressed because one or more lines are too long
Before Width: | Height: | Size: 318 KiB After Width: | Height: | Size: 318 KiB |
|
@ -2,6 +2,10 @@
|
||||||
|
|
||||||
This blueprint allows to create active/active private and/or public F5 BigIP-VE load balancers.
|
This blueprint allows to create active/active private and/or public F5 BigIP-VE load balancers.
|
||||||
|
|
||||||
|
<p align="center">
|
||||||
|
<img src="diagram.svg" alt="Networking diagram">
|
||||||
|
</p>
|
||||||
|
|
||||||
## Design notes
|
## Design notes
|
||||||
|
|
||||||
- The blueprint supports by default two VPCs: a `dataplane` network and a `management` network.
|
- The blueprint supports by default two VPCs: a `dataplane` network and a `management` network.
|
||||||
|
|
Loading…
Reference in New Issue