Add dynkeepalived to solve interface changes #20
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Using runtimecfg render for keepalived has the issue that on 1.x
keepalived versions there's no dynamic interfaces and in case the
interface changes, keepalived will stop doing its job.
Thanks to dynkeepalived, it is now possible to have it monitor the
interface and dynamically send a reload to a unix socket that can be
used to trigger a keepalived reload in the keepalived container.
This is meant to be used from a side-car to the keepalived pod.
Signed-off-by: Antoni Segura Puimedon antoni@redhat.com