Do not use HostPort when using --port-forward
Open
enhancement
- Dominant language
- Go
- Stars
- 2.3k
- Forks
- 303
- PR merge metrics
- No merged PRs in 30d
Description
When `port-forward` is enabled (which is by default after `v0.1.1`), the agent do not have to specify `hostPort`, and this could help avoiding potential port conflicts.
ref: #118
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing the kubectl-debug port-forward handling and review the behavior described in ref #118. Verify how the default-enabled port-forward mode currently handles hostPort, then consider the issue done when the agent no longer specifies hostPort in that mode and potential port conflicts are avoided.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- cli, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 20/100