After I deleted cloudcore, edgemesh turned on listening on ports 10000-10005. Failed to install cloudcore again
- Dominant language
- Go
- Stars
- 293
- Forks
- 145
- PR merge metrics
- No merged PRs in 30d
Description
**What happened**:
After I deleted cloudcore, edgemesh turned on listening on ports 10000-10005. Failed to install cloudcore again.

**What you expected to happen**:
**How to reproduce it (as minimally and precisely as possible)**:
**Anything else we need to know?**:
**Environment**:
- EdgeMesh version: v1.13.0
- Kubernetes version (use `kubectl version`):1.21.15
- KubeEdge version(e.g. `cloudcore --version` and `edgecore --version`):v1.13.0
- Cloud nodes Environment:
- Hardware configuration (e.g. `lscpu`):
- OS (e.g. `cat /etc/os-release`):
- Kernel (e.g. `uname -a`):
- Go version (e.g. `go version`):
- Others:
- Edge nodes Environment:
- edgecore version (e.g. `edgecore --version`):
- Hardware configuration (e.g. `lscpu`):
- OS (e.g. `cat /etc/os-release`):
- Kernel (e.g. `uname -a`):
- Go version (e.g. `go version`):
- Others:
Contributor guide
Research direction
Start by reproducing the cloudcore deletion and reinstall sequence with EdgeMesh v1.13.0, KubeEdge v1.13.0, and Kubernetes 1.21.15, while checking listeners on ports 10000-10005. Trace which EdgeMesh component retains or enables those listeners after deletion; done means cloudcore can be installed again without the unexpected port listeners.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100