Node port service access failed
- Dominant language
- Go
- Stars
- 293
- Forks
- 145
- PR merge metrics
- No merged PRs in 30d
Description
**What happened**:
One nodeIp is accessible and another nodeIp is inaccessible.
**What you expected to happen**:
telnet 10.31.223.12 31090 success
**How to reproduce it (as minimally and precisely as possible)**:
**Anything else we need to know?**:
**Environment**:
- EdgeMesh version: v1.14
- Kubernetes version (use `kubectl version`): v1.20
- KubeEdge version(e.g. `cloudcore --version` and `edgecore --version`): v1.12.1
- 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
No files, tests, or reproducible steps are provided. Start by reproducing the telnet test to NodePort 31090 and compare the accessible and inaccessible node IPs under EdgeMesh v1.14, Kubernetes v1.20, and KubeEdge v1.12.1; completion would require identifying the cause and documenting a verified fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100