You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@openwhisk.apache.org by GitBox <gi...@apache.org> on 2018/07/17 03:51:24 UTC

[GitHub] StrayCat1 commented on issue #257: External zookeeper kafka

StrayCat1 commented on issue #257: External zookeeper kafka
URL: https://github.com/apache/incubator-openwhisk-deploy-kube/pull/257#issuecomment-405451276
 
 
   I didn't document or test [the changes to _helpers.tpl](https://github.com/apache/incubator-openwhisk-deploy-kube/pull/257/commits/a14dddcdbe82806dfed7752d4c6faa1ec45a1f0a#diff-faa55e3a77183978b971e57a0ac048f2) well enough. 
   
   My use case includes deploying this OpenWhisk chart as dependency of another chart, so after  disabling the kafka and zookeeper defined in these charts, all I needed to do was define `kafka_host`, `zookeeper_connect`, and `zookeeper_zero_host` in my `_helpers.tpl`, but theoretically these changes would allow someone to deploy this chart into the same namespace as an existing zookeeper and kafka service by configuring their hostnames in `mycluster.yml` like this
   ```yaml
   kafka:
     external: true
     name: <existing kafka service>
   
   zookeeper:
     external: true
     name: <existing zookeeper service>
   ```

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services