Consul data plane is replacing consul client agent running in the cluster. How to hit consul HTTP API ? Documentation seems to be outdated

[MageshSrinivasulu]

With the introduction of the consul data plane, the consul client daemon set is getting removed in the Kubernetes.

The documentation seems to be outdated for hitting the consul HTTP API https://developer.hashicorp.com/consul/docs/k8s/installation/install#accessing-the-consul-http-api

Pods cannot reach the consul HTTP API with **${HOST_IP}:8500** since the client agent is not running in the node any more

Do you know if we need to hit the consul server endpoint directly in the future? consul-server.consul.svc.cluster.local:8500