Skip to content
This repository has been archived by the owner on Aug 19, 2020. It is now read-only.

Start kube-keepalived-vip via dumb-init #69

Merged
merged 1 commit into from
Dec 4, 2018

Conversation

elemental-lf
Copy link
Contributor

Best practice would be to put dumb-init into the ENTRYPOINT and kube-keepalived-vip into CMD. This commit puts both of them into ENTRYPOINT to be backwards compatible with current deployments which overwrite CMD.

I've tested the resulting image as a replacement for a deployment which has been running 0.29 up to now and have found no issues so far. Everything is as expected.

Fixes #66

Signed-off-by: Lars Fenneberg lf@elemental.net

Best practice would be to put dumb-init into the ENTRYPOINT and
kube-keepalived-vip into CMD. This commit puts both of them into
ENTRYPOINT to be backwards compatible with current deployment which
overwrite CMD.

Fixes aledbf#66

Signed-off-by: Lars Fenneberg <lf@elemental.net>
@aledbf aledbf merged commit 8d02f20 into aledbf:master Dec 4, 2018
@aledbf
Copy link
Owner

aledbf commented Dec 4, 2018

@elemental-lf thanks!

@coveralls
Copy link

Coverage Status

Coverage remained the same at 16.54% when pulling 6196d67 on elemental-lf:dumb-init into 2917558 on aledbf:master.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants