[GitHub] [pulsar-client-node] krvarma commented on issue #87: npm install fails on MacOS

krvarma commented on issue #87: URL: https://github.com/apache/pulsar-client-node/issues/87#issuecomment-629759202 `brew install libpulsar` and then `npm install pulsar-client` worked without any issues on macOS Catalina Th

[GitHub] [pulsar-manager] jiazhai commented on issue #299: Unable to get anything about a partition: TypeError: Cannot read property 'status' of undefined

jiazhai commented on issue #299: URL: https://github.com/apache/pulsar-manager/issues/299#issuecomment-629909120 @rueian How is the topic created? And which version is running in broker side? Looks like topic is not auto created. ---

[GitHub] [pulsar-manager] rueian commented on issue #299: Unable to get anything about a partition: TypeError: Cannot read property 'status' of undefined

rueian commented on issue #299: URL: https://github.com/apache/pulsar-manager/issues/299#issuecomment-629927430 I am running pulsar 2.5.1, manager 0.1.0, and I am sure the topic is auto created. I can run pulsar-admin to get its info. --

[GitHub] [pulsar-helm-chart] lukestephenson opened a new pull request #12: Support load balance source ip range

lukestephenson opened a new pull request #12: URL: https://github.com/apache/pulsar-helm-chart/pull/12 Grafana and pulsar manager now support restricting the available IPs that can be used. Note, this is my first experience with helm, so it may not be the most appropriate approach