TLDR; use http://config-binding-service:10000/

As all ONAP MS are targeted on K8S deployments (since R3), the current logic for CBS service lookup can be switched to use the k8s service definition of configbinding.

Under current deployment, CBS is deployed as "config-binding-service" k8s service under env "CONFIG_BINDING_SERVICE".

kubectl get svc -n onap | grep config
config-binding-service          NodePort       10.43.206.210   <none>                                 10000:30415/TCP                                                              4d11h

CBS Library currently depends on Consul lookup to identify CBS services (using ServiceAddress and ServicePort); k8s servicename exposed via env can be used to query the CBS API directly rather than looking up through consul (which is added un-necessary step)