aylei / aylei/kubectl-debug

How to only use target pod network?

Open
#108 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
2.3k
Forks
303
PR merge metrics
No merged PRs in 30d

Description

Hi, I want to debug the target pod why it can't access some external host.
But when I use kubectl debug with port-forward mode, it can access the external host.
It seemingly access the external host via debug-pod network.

So is there an solution only using target pod network? (for example, logon cluster host and run kubectl debug without port-forward)

Contributor guide

No contributing guide indexed for this repository

Research direction

No source files or tests are named in the issue. Start by reviewing kubectl-debug's documented debug modes and Kubernetes pod networking behavior; done would require determining whether target-pod-only networking is supported and documenting or implementing a clear solution, while noting that the repository points users to a successor project.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes
Domain
cli, devops, networking
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.