Can't figure out how to get kubernetes connection working

[Aaron Newsome <aa...@gmail.com>]

Hello all. I've been using Guacamole daily since 2017. I've done
troubleshooting on my share of issues along the way. Usually, scouring the
forums, reading and re-reading the docs will help me sort out any issues.
However, I just can't seem to figure out how to make a kubernetes
connection work.

I recently upgraded to Guacamole/Guacd v1.5.1.

After stumbling through exactly how to get the cert values needed to make
the connection (docs weren't at all helpful), I'm now getting an error from
guacd that the websocket upgrade failed. Here's the exact error message:








*guacd[1]: INFO: Creating new client for protocol "kubernetes"guacd[1]:
INFO: Connection ID is "$2bfa1cfd-43ba-4ed3-8808-72623abea9a2"guacd[865]:
INFO: User "@2fd69326-f4aa-410e-8e1d-a0e892ea6605" joined connection
"$2bfa1cfd-43ba-4ed3-8808-72623abea9a2" (1 users now present)guacd[865]:
ERROR: Error connecting to Kubernetes server: HS: ws upgrade response not
101guacd[865]: INFO: User "@2fd69326-f4aa-410e-8e1d-a0e892ea6605"
disconnected (0 users remain)guacd[865]: INFO: Last user of connection
"$2bfa1cfd-43ba-4ed3-8808-72623abea9a2" disconnectedguacd[865]: INFO:
Kubernetes connection ended.guacd[1]: INFO: Connection
"$2bfa1cfd-43ba-4ed3-8808-72623abea9a2" removed.*

I've attached a screenshot of the settings for the connection. The
connection parameters all seem correct, I can pull the resources from the
namespace with kubectl:
















*kubectl -n swift-media-manager get allNAME
      READY   STATUS    RESTARTS
AGEpod/swift-media-manager-8469dc7f6c-8qx2n   1/1     Running   0
 26dNAME                             TYPE           CLUSTER-IP
 EXTERNAL-IP      PORT(S)
AGEservice/swift-media-manager      NodePort       10.105.213.29   <none>
        80:30825/TCP,5432:30777/TCP   106dservice/swift-media-manager-lb
LoadBalancer   10.101.41.78    192.168.112.25   80:32150/TCP,5432:32173/TCP
  106dNAME                                  READY   UP-TO-DATE   AVAILABLE
  AGEdeployment.apps/swift-media-manager   1/1     1            1
106dNAME                                             DESIRED   CURRENT
READY   AGEreplicaset.apps/swift-media-manager-5f8955ff48   0         0
    0       40dreplicaset.apps/swift-media-manager-67f4fd688f   0         0
        0       34dreplicaset.apps/swift-media-manager-6d4649d49f   0
  0         0       38dreplicaset.apps/swift-media-manager-78f778577d   0
      0         0       43d*

The kubectl command uses a ~/.kube/config with the same values as used in
the connection parameters.

Has anyone been able to successfully create a Kubernetes connection? Is
there some kind of magic I'm missing?

Thanks, Aaron