Does burrow have a hard dependency on zookeeper?

I'm wondering if it's possible to use burrow in a way that it doesn't depend on having access to zookeeper.

It looks like there is a [Consumer-Kafka](https://github.com/linkedin/Burrow/wiki/Consumer-Kafka) that can consume offsets directly from Kafka.

However, it looks like burrow may [depend on Zookeeper](https://github.com/linkedin/Burrow/wiki/Configuration#zookeeper) for other internal storage.

>The [zookeeper] heading specifies a Zookeeper ensemble to use in order to store metadata for modules and provide locking between multiple copies of Burrow. This allows you to run multiple copies of Burrow with only one being allowed to execute the notifiers at any time.

It also looks like the code will always attempt to setup a Zookeeper coordinator:

https://github.com/linkedin/Burrow/blob/a449cc412c48231a2b7347cd790f82b8ed18faf2/core/burrow.go#L36-L44

Is there a way to disable requiring zookeeper for a single-instance deployment of burrow?

Thanks for the great library!

Start with core/burrow.go at the linked coordinator setup and compare it with the Zookeeper configuration documented in the wiki. Check how Consumer-Kafka obtains offsets and determine whether a single-instance deployment can avoid the coordinator. Done means the supported behavior and any required configuration are clear and covered by appropriate documentation or tests.

Written by the indexing model from the issue text.