Skip to content

fix(viz/tap): avoid empty path segment when tapping a resource kind - #15487

Open
amarkdotdev wants to merge 1 commit into
linkerd:mainfrom
amarkdotdev:fix/tap-empty-resource-name-path-5219
Open

fix(viz/tap): avoid empty path segment when tapping a resource kind#15487
amarkdotdev wants to merge 1 commit into
linkerd:mainfrom
amarkdotdev:fix/tap-empty-resource-name-path-5219

Conversation

@amarkdotdev

Copy link
Copy Markdown

Fixes #5219

Tapping a whole resource category (linkerd tap po) builds a URL with a blank name segment (.../pods//tap). Some API servers, including k3d/k3s, reject that with unexpected EOF. Named resources still worked.

Collection taps now use .../pods/tap, and the tap API registers a matching route.

Testing

  • go test ./viz/tap/pkg/ ./viz/tap/api/ -count=1

When tapping a whole category (e.g. `linkerd tap po`), the request name
is empty. The old URL had a blank segment (`.../pods//tap`), which some
API servers (notably k3d/k3s) reject with unexpected EOF.

Use `.../pods/tap` for collection taps and register a matching route.

Fixes linkerd#5219

Signed-off-by: amarkdotdev <amarkdotdev@users.noreply.github.com>
@amarkdotdev
amarkdotdev force-pushed the fix/tap-empty-resource-name-path-5219 branch from 1086406 to 0fbafaa Compare July 21, 2026 19:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

EOF when running linkerd tap command against a category of resources on a k3d cluster

1 participant