-
Notifications
You must be signed in to change notification settings - Fork 121
Update configure-high-availability.md #1243
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
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."
|
🎉 Thank you for your contribution! It appears you have not yet signed the F5 Contributor License Agreement (CLA), which is required for your changes to be incorporated into an F5 Open Source Software (OSS) project. Please kindly read the F5 CLA and reply on a new comment with the following text to agree: I have hereby read the F5 CLA and agree to its terms 2 out of 3 committers have signed the CLA. |
|
LGTM: in newer documentation we typically refer to this kind of use case as "Virtual environment or bare metal". @TheNerd02 you'll need to sign the CLA with a comment before this PR is eligible for merge. |
|
I am merging this PR, @TheNerd02 , if you want to contribute again in the future, please accept the CLA |
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."
Proposed changes
Checklist
Before sharing this pull request, I completed the following checklist:
Footnotes
Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩