yabinmeng

# Description I have a single 1-node Pulsar cluster (not running in standalone mode) and I'd like to test out using a standalone Pulsar-heartbeat to monitor the health of the...

After launching a Pulsar cluster using the helm chart, the proxy pod consumes significant CPU resources although there is no traffic. The following is copied from "kubectl describe node" command...

Duplicate definition for pulsarexpress and zoonavigator extras in values.yaml file (under pulsar sub-folder)

1

pulsarexpress: line# 258 and line# 283 zoonavigator: line# 260 and line# 281 I believe the settings on the latter location will override the other

Using "all-component-tls" example [values.yaml file](https://github.com/datastax/pulsar-helm-chart/blob/26b1248c3754b8429202d87ec2cd72f74a73ac9b/examples/dev-values-tls-all-components.yaml), I can see that the function worker always have both ports enabled. ```% kubectl describe cm pulsar-function | grep workerPort workerPort: "6750" workerPortTls: "6751" ```...

Bump up zoonavigator version

2

The current zoonavigator docker image version in the helm chart is 0.6 which is deprecated. Bump up the version to the latest version.

Allow direct message replaying by exposing Pulsar API's seek() function

1

When we use Pulsar as the underlying message processing platform, one big benefit is to allow message replaying. This feature is beyond the capability of existing JMS technologies although it...

[Geo-replication] Subscription replication is not working across clusters

26

**Describe the bug** I'm testing geo-replication with subscription enabled. In my testing environment, there are 2 clusters (ClusterA and ClusterB) with a global zookeeper on a dedicated server host. Each...