Automate SSH tunnels

Open
#49 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale

Research direction

The issue names no files, tests, or existing entry points. Start by inspecting the repository's deployment and provisioning context, then define the SSH tunnel tooling requirements, monitoring behavior, and re-establishment policy; done means a ready-to-use solution is specified and validated for both control-client and service-client domain sockets.

Written by the indexing model from the issue text.

Description

enhancement feedback research

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.

Dominant language
Haskell
Stars
2
Forks
13
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from IntersectMBO/kes-agent

All issues in IntersectMBO/kes-agent

Similar issues

More Haskell issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.