Closed cornelius-keller closed 5 years ago
/assign @bprashanth
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale
/remove-lifecycle stale
@mikedanese or @bprashanth can you tell us how to move this forward? Or give us a name that could help us get this merged? Thanks!
@pierreozoux You might want to try the better maintained fork: https://github.com/aledbf/kube-keepalived-vip/
@steven-sheehy I'd prefer an "official image". I'd like to avoid images maintained by third parties. If there is none, then okay, I'll have to maintain my fork, and build my own image. But if the official project delivers one, it would simplify the life of number of people including me.
@pierreozoux I totally agree that it is best to have this in the official image and not maintain a custom fork of it. @mikedanese @bprashanth would be nice if we can get at least a review. If there are changes required I am willing to put further effort into this but without having a clue what is missing this is difficult.
Will that ever be included?
Is there any update on this PR? It would be great seeing this in the official image.
@kubernetes/sig-network-pr-reviews
Hi all, can this be reviewed and merged guys?
fyi: as per @steven-sheehy's suggestion this has already been merged into https://github.com/aledbf/kube-keepalived-vip/ (PR: https://github.com/aledbf/kube-keepalived-vip/pull/79)
/lgtm /approve
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: bowei, cornelius-keller
The full list of commands accepted by this bot can be found here.
The pull request process is described here
Hi, i modified keepalived-vip to add an option to use notify scripts. My change should be 100% backwards compatible to the previous behavior. It is enabled by mounting your notification script to the pod via a configmap, and then setting the env var
KEEPALIVED_NOTIFY
to the location where it is mounted. This will include a line like:notify /opt/your-notify-script.sh
to the keepalived config.I use this feature on cloud providers were you need a special api call to get an failover / floating IP routed to your machine.
I would like to have this merged so that I don't have to maintain a fork of keepalived-vip.