Mortom123 commented on issue #460: URL: https://github.com/apache/pulsar-helm-chart/issues/460#issuecomment-1948285438
I'm currently investigating - https://github.com/Mortom123/pulsar-helm-chart/pull/3. And it seems the pulsar-manager test is only a symptom, and not the complete picture (at least from my understanding). To see what I mean have a look here: https://github.com/Mortom123/pulsar-helm-chart/actions/runs/7928137620 - kube-prometheus test fails https://github.com/Mortom123/pulsar-helm-chart/actions/runs/7930141638 - TLS fails https://github.com/Mortom123/pulsar-helm-chart/actions/runs/7929918393/job/21651157455 - Pulsar Manager fails They all have one thing in common - they try to access the broker. Furthermore, looking through the errors it becomes evident that all of these test fail because they cannot connect to the broker. See [here ](https://github.com/Mortom123/pulsar-helm-chart/actions/runs/7929918393/job/21651157455#step:6:5503) in the case of the manager problem. Maybe something with this [code ](https://github.com/apache/pulsar-helm-chart/blob/master/charts/pulsar/templates/proxy-statefulset.yaml#L129) is not working as expected? Or the broker encounters an error and starts to restart? -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
