[Question] <title>I am unable to deploy the collector.

### Question

I am unable to deploy the collector.😭

background：The version I am using is v1.6.0. The current issue is that I want to use the Collector Cluster feature, but the collector cannot be deployed.

The docker collector command used
` docker run -d -e IDENTITY=12345 -e MODE=public -e MANAGER_HOST= -e MANAGER_PORT=1158 --name hertzbeat-collector apache/hertzbeat-collector:v1.6.0`
> I have tried Laster. Still not working.

The configuration is as follows.
application.yaml


In hertzbeat-server curl 1158


hertzbeat-server port is listed


Use ingress domain to map 1157

Now looking hertzbeat-collector logs

error log description

```
2025-05-13 13:47:18.806 [common-worker-0] ERROR org.apache.hertzbeat.remoting.netty.NettyRemotingClient Line:107 - client connect to
server error: Connection refused: obs-hertzbeat-cluster/192.168.6.108:1158. try after 10s.
```

> Cluster service type is ClusterIP

ok log description

```
2025-05-13 21:56:38.840 [heartbeat-worker-0] INFO org.apache.hertzbeat.collector.dispatch.entrance.CollectServer Line:165 - collect
or send cluster server heartbeat, time: 1747144598840.
2025-05-13 21:56:38.840 [netty-client-worker-1] INFO org.apache.hertzbeat.collector.dispatch.entrance.processor.HeartbeatProcessor
Line:32 - collector receive manager server response heartbeat, time: 1747144598840.
```

Start by reviewing the collector error log and the Docker command, then compare MANAGER_HOST and MANAGER_PORT with the server's ClusterIP service and ingress configuration. Confirm the collector can reach port 1158 and that its logs show a successful heartbeat response; the issue does not name source files or tests.

Written by the indexing model from the issue text.