Closed sssd-dev closed 2 years ago
After enabling tls on broker and disabling port 8080, pulsar hearbeat init container is still trying to connect to port 8080.
https://github.com/datastax/pulsar-helm-chart/blob/pulsar-2.1.3/helm-chart-sources/pulsar/templates/pulsar-heartbeat/pulsar-heartbeat-deployment.yaml#L71
curl command should be trying to connect to port 8443 after enabling tls on broker by hitting https endpoint instead of currently configured http.
https
http
Thanks for creating this issue @sssd-dev. I agree that the heartbeat should use the https port when enableTls: true.
enableTls: true
After enabling tls on broker and disabling port 8080, pulsar hearbeat init container is still trying to connect to port 8080.
https://github.com/datastax/pulsar-helm-chart/blob/pulsar-2.1.3/helm-chart-sources/pulsar/templates/pulsar-heartbeat/pulsar-heartbeat-deployment.yaml#L71
curl command should be trying to connect to port 8443 after enabling tls on broker by hitting
https
endpoint instead of currently configuredhttp
.