[GitHub] [pulsar-helm-chart] DonghunLouisLee commented on issue #72: Please add support for Tiered Storage in the Helm Chart

DonghunLouisLee commented on issue #72: URL: https://github.com/apache/pulsar-helm-chart/issues/72#issuecomment-729329156 > Nono, when you change the charts you cannot use the same chart, so I repackaged locally and applied those! Not as fancy haha Ideally these should go into the officia

[GitHub] [pulsar-helm-chart] devinbost commented on issue #84: TLS Authentication in Kubernetes, Pulsar 2.6.1 - Broker crash loop on startup due to 401 in WorkerService.start(..)

devinbost commented on issue #84: URL: https://github.com/apache/pulsar-helm-chart/issues/84#issuecomment-729305401 Just before the exception is thrown, it appears that the broker is successfully able to establish a TLS session with Zookeeper, but then it gives this odd message: ``

[GitHub] [pulsar-helm-chart] devinbost edited a comment on issue #84: TLS Authentication in Kubernetes, Pulsar 2.6.1 - Broker crash loop on startup due to 401 in WorkerService.start(..)

devinbost edited a comment on issue #84: URL: https://github.com/apache/pulsar-helm-chart/issues/84#issuecomment-729301860 It appears (from the debug logs) that the TLS session is established. The exception "Client unable to authenticate with TLS certificate" is thrown in Authentication

[GitHub] [pulsar-helm-chart] devinbost commented on issue #84: TLS Authentication in Kubernetes, Pulsar 2.6.1 - Broker crash loop on startup due to 401 in WorkerService.start(..)

devinbost commented on issue #84: URL: https://github.com/apache/pulsar-helm-chart/issues/84#issuecomment-729301860 It appears (from the debug logs) that the TLS session is established. The exception "Client unable to authenticate with TLS certificate" is thrown in AuthenticationProvide

[GitHub] [pulsar-helm-chart] devinbost commented on issue #84: TLS Authentication in Kubernetes, Pulsar 2.6.1 - Broker crash loop on startup due to 401 in WorkerService.start(..)

devinbost commented on issue #84: URL: https://github.com/apache/pulsar-helm-chart/issues/84#issuecomment-729225278 I added TLS debugging. (I forgot to tag this issue in the commit.) This is an automated message from the Apa

[GitHub] [pulsar-helm-chart] axel-sirota commented on issue #72: Please add support for Tiered Storage in the Helm Chart

axel-sirota commented on issue #72: URL: https://github.com/apache/pulsar-helm-chart/issues/72#issuecomment-729036916 Nono, when you change the charts you cannot use the same chart, so I repackaged locally and applied those! Not as fancy haha Ideally these should go into the official char

Pulsar Community Weekly Update] 2020-11-07 ~ 2020-11-13

Dear Pulsar enthusiast, This is the Pulsar community weekly update for 2020-11-07 ~ 2020-11-13, with updates on Pulsar client, broker, transaction, and so on. This Pulsar community weekly update is also available at https://streamnative.io/weekly/2020/2020-11/2020-11-13-pulsar-weekly. *All Pulsa

[ANNOUNCE] Apache Pulsar Client Go 0.3.0 released

The Apache Pulsar team is proud to announce Apache Pulsar Client Go version 0.3.0. Pulsar is a highly scalable, low latency messaging platform running on commodity hardware. It provides simple pub-sub semantics over topics, guaranteed at-least-once delivery of messages, automatic cursor managemen

Re: [VOTE] Pulsar Client Go Release 0.3.0 Candidate 1

The vote is now closed for pulsar-client-go 0.3.0 Release Candidate 1 with 6 "+1” (3 +1 binding votes) votes, 0 +0/-0 votes, 0 -1 votes. 3 +1 bindings are: PengHui Li Hiroyuki Sakai Jia Zhai 3 +1 non-binding are: Xiaolong Ran Guangning E Yuto Furuta — Thanks Xiaolong Ran > 在 2020年11月11日，下午6:53

Re: [VOTE] Pulsar Client Go Release 0.3.0 Candidate 1

+1 Best Regards. Jia Zhai Beijing, China Mobile: +86 15810491983 On Mon, Nov 16, 2020 at 5:30 PM PengHui Li wrote: > +1 (binding) > On Nov 12, 2020, 12:53 PM +0800, Hiroyuki Sakai , > wrote: > > +1 (binding) > > > > - Verify checksum > > - Verify gpg key > > - Run producer and consumer >