[GUACAMOLE-1634] Bad error handling in Kubernetes protocol

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Component/s: guacamole-server, Kubernetes
• Assignee: Unassigned
• Reporter: James Muehlner
• Created: 11/Jul/22 20:42
• Updated: 11/Jul/22 20:42

Description

When the connection parameters are set incorrectly for a Kubernetes connection, the server logs do not display any useful information, even if there is a human-readable error sent back from Kubernetes.

For example: I tried to connect to a pod without specifying the namespace. The error I got in the guacd logs was: `Error connecting to Kubernetes server: HS: ws upgrade response not 101`.

However, I've attached a screenshot of the wireshark logs showing that the namespace error was correctly sent by Kubernetes. This error should be properly handled and logged so the user can easily see what went wrong.