replicatedhq / replicatedhq/kURL
Connectivity Issue: Unable to Telnet to Kubernetes Services from Nodes Other Than the Deployment Node
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 809
- Forks
- 81
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 20
Description
The presented issue revolves around a Kubernetes cluster that has been successfully installed using kurl on Ubuntu 22. All Kubernetes pods appear to be functioning as expected without any apparent disruptions. However, a critical connectivity problem happend, preventing from establishing Telnet connections to the services hosted within the cluster from nodes other than the node where the services' pods are deployed.
Upon initial observation, the Kubernetes cluster appears to be functioning correctly, with pods running, services deployed, and overall cluster health indicating normal operations. Despite this seemingly healthy state, attempts to Telnet to the services from nodes other than the specific node hosting the corresponding pods result in failure.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no repository files, tests, logs, or entry points. Start by reproducing the failed Telnet access between Ubuntu nodes in the kURL-installed Kubernetes cluster and inspect the service and node-networking configuration; done means service connectivity works from nodes other than the pod's node.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, ubuntu
- Domain
- infrastructure, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100