Search before reporting

• I searched in the issues and found nothing similar.

Motivation

Pulsar Admin client creates it's own AsyncHttpClient with a Netty event loop, timer and DNS resolver and cache. In use cases where it is desired to reduce resource usage and share the DNS settings in the admin client, it would be useful if the Pulsar Admin client would also support PulsarClientSharedResources. PIP-234 implementation #24790 adds support for sharing thread pools and DNS resolver/cache across multiple client instances with PulsarClientSharedResources API.

Solution

Adding sharedResources to the builder and using the resources for the AsyncHttpClient instance.

Alternatives

No response

Anything else?

No response

Are you willing to submit a PR?

• I'm willing to submit a PR!