Dynamically reading burrow config

Burrow currently does not reload when config file changes, but viper supports the feature of watching config file for changes and could reload it if changed.
Can we have the ability to restart burrow whenever the config file changes ?

Currently I have burrow deployed on kubernetes and I have attached a sidecar which would send kill -1 to the burrow process whenever its config is updated. However this results in the container going into crashloopbackoff everytime config is updated and during this entire duration it creates downtime. So I was looking for a way to just make burrow read its config file dynamically

Start by locating Burrow's config-loading entry point and reviewing Viper's support for watching config files. Define how a change should reload configuration in place without the Kubernetes container exiting, then add coverage showing that updated configuration takes effect without downtime.

Written by the indexing model from the issue text.