Details
-
New Feature
-
Status: Resolved
-
Minor
-
Resolution: Done
-
None
-
None
Description
Currently, guacd can only access the terminals of containers in Kubernetes pods if those containers host services that use the protocols guacd already supports, such as an SSH daemon. This works, but is suboptimal: a container should ideally be dedicated to one logical application.
Kubernetes provides a web service / API through which an application can attach to the terminal of a container. Leveraging this API, support for attaching to a container and accessing its terminal could be added to guacd, functioning essentially identically to the way SSH and telnet support currently works.