hjohannsen commented on issue #6135: Unable to deploy on GKE, blocked at bookie.yaml step URL: https://github.com/apache/pulsar/issues/6135#issuecomment-581490632 We're facing the same issue with AWS EKS. The [apply-config-from-env.py](https://github.com/apache/pulsar/blob/master/docker/pulsar/scripts/apply-config-from-env.py) script doesn't strip away the `PULSAR_PREFIX_` when overwriting _existing_ keys. So, if a key, such as `zkServers` already exists in the `bookkeeper.conf`, the setting isn't overwritten. In the [EKS deployment sources](https://github.com/apache/pulsar/tree/master/deployment/kubernetes/aws) which we departed from, the `zkServers` env variable is defined _with_ the prefix (`PULSAR_PREFIX_zkServers`). And in the config from the Docker image the setting already exists: `zkServers=localhost:2181`. As a consequence, overwriting doesn't happen and the Bookkeeper looks for the Zookeeper at `localhost` instead of `zk-x.zookeeper`. Our temporary workaround is to duplicate the settings in the `ConfigMap`, with and without prefix. Is there any reasoning behind ignoring the prefix for existing keys or is it just a bug?
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
