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

Enhancement: Make init try loop optional via envvar setting #17

Open
jspaleta opened this issue Feb 22, 2021 · 0 comments
Open

Enhancement: Make init try loop optional via envvar setting #17

jspaleta opened this issue Feb 22, 2021 · 0 comments
Labels
enhancement New feature or request

Comments

@jspaleta
Copy link

init loop is great for single backend using embedded etcd.
For more complicated situations with multiple backends or external etcd, it might be good to give users the ability to disable the init loop logic so they can explicitly handle init via a means they control.

For example in k8s, an explicit initcontainer might be best for a statefulset configuration.

Implementation Proposal

have new envvar in entrypoint.sh DISABLE_BACKEND_INIT, if set skip the init wait loop logic entirely.

@echlebek echlebek added the enhancement New feature or request label Mar 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants