Skip to content

[P2] Handle tuple request timeouts consistently in pod exec #18

Open

Description

@brendandburns

Upstream: kubernetes-client#2292
Priority: P2 (WebSocket API consistency)

Passing _request_timeout=(connect_timeout, read_timeout) to pod exec is reported to fail with a float-versus-tuple comparison error. The REST transport supports a timeout tuple, but the WebSocket path passes the value into its run loop without equivalent handling.

Reproduce on the current client and define supported connect/read timeout semantics for exec. Do not silently drop one tuple component or conflate connection timeout with command duration.

Acceptance criteria:

  • Add focused tuple-timeout regression coverage.
  • Preserve supported scalar/default timeout and non-preloaded streaming behavior.
  • Document any transport-specific constraints and surface unsupported values explicitly.

Activity

  1. linked a pull request that will close this issueHandle tuple request timeouts in pod exec #30on Nov 19, 2026
  2. brendandburns commented on Nov 19, 2026

    @brendandburns
    OwnerAuthor

    Clarification to the original assignment: this task's designated agent/base branch is agent/p2-issue-18. Raise/target the PR against that branch, not master; the existing draft PR has been retargeted accordingly. Keep the requested commit order: first a test-only commit demonstrating the issue, then a separate fix commit only if reproduced. If it does not reproduce, leave the evidence/test commit and explain why no fix is appropriate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

bugSomething isn't working

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions