No healthy upstream with service mesh and namespace

### Problem description

Node js grpc call is returning no healthy upstream when the services are configured behind service mesh with namespace.

### Reproduction steps

The gRPC services are developed in GoLang, and deployed in Kubernetes cluster in multiple namespaces. These services are accessed through service mesh, redirecting to the respective namespace based on URL.

Example: service-mesh-host/namespace

Node js is failing to connect with no healthy upstream issue. Postman and other tools were able to connect without any issue.

Node js is working when single namespace is there, we could able to route without namespace in URL and hardcoded namespace inside service mesh route.

### Environment
- OS name, version and architecture: [macOS Monterey 64 bit]
- Node version [v20.3.1]
- Node installation method [nvm]
- Package name and version [e.g. gRPC@1.8.16]