GitHub user sindhushreem25 added a comment to the discussion: DNS
@lhotari We have a scenario like we pulsar pods deployed in Kubernetes namespace< pulsar> and client pods deployed in other namespace<tenant1> . when the client tries to talk to pulsar proxy pods we provide the service url and pulsar url like https://pulsar-proxy. pulsar:8443 this internal will resolve to https://pulsar-proxy.pulsar.svc.cluster.local:8443 and this connection works and clients are able to communicate with pulsar server . but there are additional search DNS happening in the client side for other entries in etc/resolve.conf which may not be correct . but this incorrect connections is tried in specific intervals again and again and logs in proxy logs . As suggested i tried to give the trailing dot but the resolution will stop at https://pulsar-proxy.pulsar:8443 which will not work for cross namespace Kubernetes communication . GitHub link: https://github.com/apache/pulsar/discussions/24030#discussioncomment-12383349 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
