Skip to content

[v16] [kube] return Kubernetes API errors when using Websocket API#46811

Merged
tigrato merged 1 commit intobranch/v16from
bot/backport-46796-branch/v16
Sep 20, 2024
Merged

[v16] [kube] return Kubernetes API errors when using Websocket API#46811
tigrato merged 1 commit intobranch/v16from
bot/backport-46796-branch/v16

Conversation

@tigrato
Copy link
Copy Markdown
Contributor

@tigrato tigrato commented Sep 20, 2024

Backport #46796 to branch/v16

changelog: Fixes a regression where Teleport swallowed Kubernetes API errors when using kubectl exec with a Kubernetes cluster newer than v1.30.0.

Kubernetes 1.30 introduced a new Remote Command protocol that uses WebSockets, replacing the deprecated SPDY protocol. The new executor protocol didn't returned the status error when API call failed.

For Teleport, this creates an issue because permission errors are absorbed by the WebSocket executor and were never passed to users.

This pull request implements a status parser for websocket Kubernetes API error.

Signed-off-by: Tiago Silva <tiago.silva@goteleport.com>
@tigrato tigrato added this pull request to the merge queue Sep 20, 2024
Merged via the queue into branch/v16 with commit f3eaa78 Sep 20, 2024
@tigrato tigrato deleted the bot/backport-46796-branch/v16 branch September 20, 2024 17:18
@camscale camscale mentioned this pull request Sep 25, 2024
@fheinecke fheinecke mentioned this pull request Apr 9, 2025
@fheinecke fheinecke mentioned this pull request Jan 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants