Skip to content

Commit 4859886

Browse files
authored
Update configure-high-availability.md (#1243)
The documentation mentions 2 physical server, implying the configuration can only be applied when hardware servers are being used not virtual machines. However below that There are some caveats about using cloud platforms (implying it would be possible to apply this configuration to the cloud as well) "Some cloud platforms don’t allow direct IP management with keepalived. If you’re using a cloud environment, check whether it supports VIP assignment."
1 parent 8aeaa0f commit 4859886

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

content/nim/system-configuration/configure-high-availability.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ This guide shows how to configure HA for NGINX Instance Manager using `keepalive
2525

2626
Before setting up high availability (HA) for NGINX Instance Manager, make sure you have:
2727

28-
- Two physical servers with NGINX Instance Manager installed
28+
- Two servers with NGINX Instance Manager installed
2929
- A reserved virtual IP address (VIP) that always points to the active instance
3030
- An NFS share that both servers can access
3131
- Permissions to manage IP addresses at the operating system level
@@ -258,4 +258,4 @@ If failover does not work as expected, check the following:
258258

259259
## Need help?
260260

261-
For additional support, visit the [F5 Support Portal](https://support.f5.com).
261+
For additional support, visit the [F5 Support Portal](https://support.f5.com).

0 commit comments

Comments
 (0)