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.

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

kube-keepalived-vip - keepalived instance template access needed #393

Open
bdowling opened this issue Mar 8, 2024 · 1 comment
Open
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@bdowling
Copy link

bdowling commented Mar 8, 2024

The repo https://github.com/openelb/kube-keepalived-vip does not have issues enabled, so posting this here for now.

With the issues I ran into in #392 I considered going back to VIP mode given the HA provided by keepalived (when it doesn't keep crashing!), might be useful.

However in thinking about doing this I realized that there may be conflicts with virtual_router_id with multiple instances/clusters on the same network.

This, among other customizations, I believe the template used for the keepalived.tmpl should be made available as a config-map in the cluster so the user can adjust as needed.

Also concerned about the flushing of IPVS tables when keepalived starts up, so access to the daemonset deployment template would also be useful, though I realize this could be edited after the cluster is deployed, with openelb managing that it feels there may be another mechanism needed to edit, or just leave deployment of that outside of openelb, which would help address the issue of not running keepalived when the user intends not to use vip mode. #390

@OAMchronicle
Copy link

Can I understand that your virtual_router_id is duplicated

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

2 participants