[bug] deploy is blocked

### Search before asking

- [X] I had searched in the [issues](https://github.com/labring/laf/issues?q=is%3Aissue) and found no similar issues.

### Environment

Linux (self-host)

### What happened

The deployment process is blocked

`
4ce131c97348fe55eddc2744af1dc3b0935245a45d8adfd6e1048b11b1deb666
6a1adc29fae9aad70c142ac5441bb31a86b2eb5b34f20ec0ce87bc7f0c3e1834
fd34b282caa91409172d78fee4523ce71ee2eeb55a623dd92c1ea455ca3e52fc
c92058596efa1a725d7ff22aff7eface53eb8764dd3b3c43fbd086b7a157ee4e
474ce0cd781b74ebca1661b7c6f6e334f157d9849ade2ed4be03a71cb419f51d
1c74006298e1cec268b08b4c525716f15ef6c1b39b74dafbabf8e569364036f8
f4740ed561d973856862bc8448f9c75fbca71cd811770a95e0124139e0f4b1c4
00cd54c81444efe0deeabdc0a5ec54c1f008e5dbf63b0ff8bc5dbc24879638cc
54f76748dae13a19351c91273b1e50a7f96cfc0f211a5be9f15bcefcaa4f1ed1
2024-04-10T10:15:08 info Start to create a new cluster: master [198.19.249.115], worker [], registry 198.19.249.115
2024-04-10T10:15:08 info Executing pipeline Check in CreateProcessor.
2024-04-10T10:15:08 info checker:hostname [198.19.249.115:22]
2024-04-10T10:15:08 info checker:timeSync [198.19.249.115:22]
2024-04-10T10:15:08 info Executing pipeline PreProcess in CreateProcessor.
2024-04-10T10:15:08 info Executing pipeline RunConfig in CreateProcessor.
2024-04-10T10:15:08 info Executing pipeline MountRootfs in CreateProcessor.
2024-04-10T10:15:08 info Executing pipeline MirrorRegistry in CreateProcessor.
2024-04-10T10:15:08 info trying default http mode to sync images to hosts [198.19.249.115:22]
2024-04-10T10:15:08 info Executing pipeline Bootstrap in CreateProcessor
INFO [2024-04-10 10:15:08] >> Check port kubelet port 10249..10259, reserved port 5050..5054 inuse. Please wait...
`

### How to reproduce

`
cd deploy

# replace with your domain here.
export DOMAIN=127.0.0.1.nip.io

# install k8s cluster
sh install-on-linux.sh $DOMAIN
`

### Are you willing to submit PR?

- [ ] Yes I am willing to submit a PR!

Start with deploy/install-on-linux.sh and reproduce the self-hosted Linux setup using DOMAIN=127.0.0.1.nip.io. Read the deployment log around the kubelet port check and determine what prevents the cluster installation from completing; done means the deployment proceeds past this blocked step.

Written by the indexing model from the issue text.