Re: [VOTE] Pulsar Release 3.1.0 Candidate 1

+1 (binding) ``` Apache Maven 3.9.3 (21122926829f1ead511c958d89bd2f672198ae9f) Maven home: /usr/local/Cellar/maven/3.9.3/libexec Java version: 17.0.7, vendor: Homebrew, runtime: /usr/local/Cellar/openjdk@17/17.0.7/libexec/openjdk.jdk/Contents/Home Default locale: en_GB, platform encoding: UTF-8 O

Re: [VOTE] Pulsar Release 3.1.0 Candidate 1

+1 (binding) ``` lipenghui@lipenghuis-MacBook-Pro apache-pulsar-3.1.0 % java -version openjdk version "17.0.7" 2023-04-18 LTS OpenJDK Runtime Environment Corretto-17.0.7.7.1 (build 17.0.7+7-LTS) OpenJDK 64-Bit Server VM Corretto-17.0.7.7.1 (build 17.0.7+7-LTS, mixed mode, sharing) lipenghui@lipen

Re: [DISCUSS] PIP 289: Secure Pulsar Connector Configuration

Hi, Sorry for the late reply. I think we can avoid adding a new config: interpolate_secrets_into_config_map. https://github.com/apache/pulsar/pull/20903#issuecomment-1674570878 Thanks, Baodi Shi On Aug 11, 2023 at 00:34:05, Michael Marshall wrote: > * Should we deprecate the old way of inje

[DISCUSS] Support storing the brokerClient certificates on ZK or BK

Hi Pulsar community, I want share some feedback about the current brokerClient certificate implementation and an idea to improve: The use case is configuring the geo-replication to a remote cluster with TLS enabled and will require to set brokerClientTlsEnabled as true and configure the broker