-
Notifications
You must be signed in to change notification settings - Fork 7
Automate SSH tunnels #49
Copy link
Copy link
Open
Labels
enhancementNew feature or requestNew feature or requestfeedbackRequires feedback from users/stakeholdersRequires feedback from users/stakeholdersresearchTasks that require research before any development can be done.Tasks that require research before any development can be done.
Description
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or requestfeedbackRequires feedback from users/stakeholdersRequires feedback from users/stakeholdersresearchTasks that require research before any development can be done.Tasks that require research before any development can be done.
Type
Fields
Give feedbackNo fields configured for issues without a type.
To connect to a remote KES agent (whether as a control client or as a service client), the relevant domain sockets need to be forwarded over SSH.
For reliable unattended operation, it is necessary to automate the process of setting up those tunnels, monitor them, and re-establish them as needed.
This should not happen from within
kes-agent, but in the interest of making it maximally easy to deploy and provision KES agent setups, we should provide some kind of ready-to-use tooling to cover this.