Skip to content
This repository has been archived by the owner on Apr 4, 2023. It is now read-only.

Don't restart service if sidekick is upgraded #20

Open
onedr0p opened this issue Sep 18, 2018 · 1 comment
Open

Don't restart service if sidekick is upgraded #20

onedr0p opened this issue Sep 18, 2018 · 1 comment

Comments

@onedr0p
Copy link

onedr0p commented Sep 18, 2018

Hi again!

Here's my use case:
We have a prometheus container deployed with a sidekick (prometheus-conf) volume for the configuration. When we deploy a new sidekick for the prometheus container we don't need it to restart the prometheus container. Instead we would have another job to reload the prometheus configuration via a curl request as described here.

I hope this makes sense. Thanks.

@onedr0p
Copy link
Author

onedr0p commented Sep 18, 2018

Looks like this might not be possible rancher/rancher#2454

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

No branches or pull requests

1 participant