feat(network): added local port forwarding

- To get this working correctly, the data and
  state management in `session` needed to be
  refactored. This is because tcpip requests
  create new channels on top of the initial one
  used via pty requests. Now the state stops at
  `Authenticated` and the functions themselves
  hold their own state (like russh_sftp taking
  ownership of the channel).
- Error handling is a little tricky, there's no
  way to return an error on the incoming tcpip
  channel (no idea what the protocol is after
  all). So, it is possible to broadcast to a
  `writer` from anywhere in the session. In the
  case of the dashboard, this results in an error
  that pops up for the user.
- Ratatui can't handle ANSI, so now the
  `color_eyre` output is correctly converted into
  a `Text` widget.
- The dashboard now takes an `impl AsyncRead`
  along with the `impl Writer` that it used to.
  This required changing the `stdin` reader in the
  dashboard dev command.
- `channel_eof` now correctly only closes the
  channel it was meant for and not the entire
  session (especially if a dashboard was running).
- As data is now owned by the request that created
  it, the session level data handler only tracks
  total bytes.

Author: grampelberg

Cargo.lock

@@ -21,6 +21,7 @@ keywords = ["cli", "kubernetes", "ssh", "tui", "terminal"]
 categories = ["command-line-interface"]
 
 [dependencies]
+ansi-to-tui = "=5.0.0-rc.1"
 async-trait = "0.1.81"
 cata = { version = "0.1.1" }
 chrono = { version = "0.4.38", features = ["serde"] }
@@ -61,15 +62,15 @@ russh = "0.45.0"
 russh-keys = "0.45.0"
 russh-sftp = "2.0.3"
 schemars = { version = "0.8.21", features = ["chrono"] }
-serde = { version = "1.0.208", features = ["derive"] }
-serde_json = "1.0.124"
+serde = { version = "1.0.209", features = ["derive"] }
+serde_json = "1.0.127"
 serde_path_to_error = "0.1.16"
 serde_yaml = "0.9.34"
 ssh-key = "0.6.6"
 strum_macros = "0.26.4"
 syntect = "5.2.0"
 syntect-tui = "3.0.3"
-tokio = { version = "1.39.3", features = ["full"] }
+tokio = { version = "1.40.0", features = ["full", "tracing"] }
 tokio-util = { version = "0.7.11", features = ["io-util"] }
 tracing = "0.1.40"
 tracing-error = { version = "0.2.0", features = ["traced-error"] }

Cargo.toml

@@ -41,3 +41,22 @@ When you run `just dev-push`, an image at `kuberift:5432/kuberift:latest` will
 be available to run inside the cluster.
 
 [k3d]: https://k3d.io/v5.6.3/#releases
+
+## Forwarding
+
+If testing port forwarding and running the service locally (aka not on the
+cluster), you won't have access to any of the DNS or IP addresses that might be
+forwarded. To work around this, modify `/etc/hosts`:
+
+```txt
+127.0.0.1 localhost.default.svc
+```
+
+Then you'll be able to test forwarding to localhost via:
+
+```bash
+ssh -L 9090:svc/default/localhost:9091 me@localhost -p 2222
+```
+
+Testing `pods` and `nodes` requires running on the cluster as the response from
+`addr` for those is IP addresses.