You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@heron.apache.org by GitBox <gi...@apache.org> on 2021/02/18 23:08:01 UTC

[GitHub] [incubator-heron] nicknezis opened a new issue #3676: The Bookkeeper hostPort used in the Helm chart conflicts when running multiple clusters

nicknezis opened a new issue #3676:
URL: https://github.com/apache/incubator-heron/issues/3676


   **Describe the bug**
   The `hostPort: 3181` which can be found [here](https://github.com/apache/incubator-heron/blob/a94533854d1db1f20e886fc51ca4bc6ef1385e2f/deploy/kubernetes/helm/templates/bookie.yaml#L165) in the Bookkeeper template in the Helm chart. This host port is not used with the standard use of Helm installed Heron. I believe this is a remnant from an older use case that is no longer valid. The use of this `hostPort` causes port conflict when running multiple Heron clusters in a Kubernetes cluster. Specifically the Bookkeeper nodes will not be able to coexist on a k8s node.
   
   **To Reproduce**
   Steps to reproduce the behavior:
   Spin up multiple Heron clusters on a single instance of Minikube
   
   **Expected behavior**
   We should be able to run multiple clusters using the K8s networking to allow for virtual ports
   


----------------------------------------------------------------
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:
users@infra.apache.org



[GitHub] [incubator-heron] nicknezis closed issue #3676: The Bookkeeper hostPort used in the Helm chart conflicts when running multiple clusters

Posted by GitBox <gi...@apache.org>.
nicknezis closed issue #3676:
URL: https://github.com/apache/incubator-heron/issues/3676


   


----------------------------------------------------------------
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:
users@infra.apache.org