Describe the bug
When attempting to connect via the proxy using an ingress with a custom URL, an error is thrown: Resolve error: asio.netdb:1 : Host not found (authoritative), presumably due to the DNS being switched from the custom URL to an internal Kubernetes URL.
Failure presumably at the changeover:
http://dev-pulsar-proxy.<redacted>.com:80 -> pulsar://pulsar-broker-2.pulsar-broker.pulsar.svc.cluster.local:6650
See below for more error details w/ full stack trace.
To Reproduce
Install Apache Pulsar Helm Chart using these configs:
Describe the bug When attempting to connect via the proxy using an ingress with a custom URL, an error is thrown:
Resolve error: asio.netdb:1 : Host not found (authoritative)
, presumably due to the DNS being switched from the custom URL to an internal Kubernetes URL.Failure presumably at the changeover:
http://dev-pulsar-proxy.<redacted>.com:80
->pulsar://pulsar-broker-2.pulsar-broker.pulsar.svc.cluster.local:6650
See below for more error details w/ full stack trace.
To Reproduce Install Apache Pulsar Helm Chart using these configs:
values.yaml (relevant snippets)
pulsar-ingress.yaml
Test the Proxy note: Tenants, Namespaces, Topics and Subscriptions replaced with for universality.
Expected behavior A connection is made through the pulsar proxy on port 80 or 443 using HTTP/HTTPS that gets converted into usable Pulsar commands.