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

Separate bird/bird6 into their own containers #56

Open
jellonek opened this issue Jun 2, 2021 · 0 comments
Open

Separate bird/bird6 into their own containers #56

jellonek opened this issue Jun 2, 2021 · 0 comments

Comments

@jellonek
Copy link
Contributor

jellonek commented Jun 2, 2021

Currently we are using a single bird container which depending on the env variables is running one or 2 daemons, then checking their liveness and if one of them died - the whole container is dying.

IMO we should instead use 2 separate containers (second one created "if needed", if ipv6 is enabled in the configuration) while the entry point for each of them should be directly bird (or bird6 in the second case), running in the foreground mode (possibly with some additional logs).

This would provide imo more k8s native way of whole thing handling (restarts) also having separately logs on consoles for both processes (e.g. right now we don't have any info why previous instance of daemon died and with which status code).

@hudymi hudymi assigned flyingklop and unassigned flyingklop Jul 12, 2021
@sj14 sj14 assigned sj14 and unassigned sj14 Oct 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants