Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Make keepalived more configurable #683

Closed
abyss-ms opened this issue Jun 28, 2024 · 2 comments
Closed

Make keepalived more configurable #683

abyss-ms opened this issue Jun 28, 2024 · 2 comments

Comments

@abyss-ms
Copy link
Contributor

It’d be nice to extend the keepalived role and make it possible to configure some options, for example, by adding the possibility of configuring more VIPs, virtual router IDs, and changing authentication. I'll prepare a PR for that and please let me know what you think about it. Thanks.
@abyss-ms abyss-ms mentioned this issue Jun 28, 2024
Merged
@vitabaks
Copy link
Owner

by adding the possibility of configuring more VIPs

@abyss-ms Could you please explain why it might be necessary to have more than one VIP address for a database cluster?

@abyss-ms
Copy link
Contributor Author

abyss-ms commented Jun 30, 2024 •
edited
Loading

Sure, in my case, there is a separate network for VPN traffic, allowing other sides to connect to the database (reporting application). Therefore, the VPN connection still has failover functionality.

vitabaks pushed a commit that referenced this issue Jul 1, 2024
@abyss-ms
Make keepalived role more configurable (issue #683) (#684)
e4b4812
@vitabaks vitabaks closed this as completed Jul 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@abyss-ms @vitabaks and others