Pod mesh networks

A mesh network connects a group of pods so you can use SSH to work from one member pod in another. Use a mesh to move files between pods, run commands on a peer, or let several agents work together. SkyDeck configures the SSH keys and host aliases automatically.

Set up a mesh network

1. In GenStudio, open Pods, then Mesh networks in the left rail.
2. Select New mesh network, or the + next to Mesh networks.
3. Enter a Network name and select at least two pods. You can add pods you own or pods shared with you with read-write access in your organization.
4. Select Create network.
5. Open the network and check its Participants. Start the pods you want to connect, and wait for both to be running.

You can include stopped pods when creating a network. SkyDeck updates running members with their mesh configuration; stopped members receive it when they next start.

Connect to another pod

1. Open a terminal in a running member pod.
2. On the mesh page, find the destination pod under Participants and copy its SSH command using the copy button.
3. Paste and run the command in the source pod's terminal. For example:

ssh analyst-pod

Use the command shown on the page rather than guessing from the display name. Aliases are lowercase and replace spaces or punctuation with hyphens, so a pod named Analyst Pod uses analyst-pod. If a pod was renamed, open Add / remove pods and select Save changes to refresh the mesh configuration, then copy the command again.

Run exit to leave the SSH session and return to the source pod's terminal.

The same destination alias works with file-transfer tools installed in your pod. For example, to copy a local file into the destination pod's durable workspace:

scp report.csv analyst-pod:/workspace/

Operate the network

The mesh diagram shows the member pods and their running status. A solid line means both pods are running; a dashed line means at least one is not running.

• Start a member: Select Start beside a stopped pod in Participants. If you cannot start it, ask its owner. Wait for the pod to be running before connecting. A pod that is still building or has an error may need attention from its owner before it can start.
• Change membership: Select Add / remove pods, update the selected pods, and select Save changes. Keep at least two pods selected.
• Rename the network: Select Rename, enter the new name, and press Enter.
• Delete the network: Select Delete and confirm. This removes the mesh; the member pods and their stored files remain.

Network editing controls are available when you have write access to a member pod. To save membership changes, you need write access to every selected pod.

A pod can belong to more than one mesh. Pods that still share another mesh keep their mesh SSH access when one network is removed or deleted. Removing membership updates SSH authorization; it does not end an SSH session that is already open.

For sleep behavior, persistent storage, and running costs, see Pods.

Troubleshooting

Problem	What to check
Create network is disabled	Select at least two pods. If a pod is missing, check that you own it or have read-write access to it.
Could not resolve hostname	Copy the destination command from Participants again, confirm both pods are in the same mesh, and start the destination if it has never run.
The connection times out or is refused	Check that both pods are running. Start stopped pods and wait for startup to finish before retrying.
Permission denied (publickey)	Confirm that both pods still share a mesh. If membership recently changed, open Add / remove pods and save the correct membership again to refresh the mesh configuration.
A membership change cannot be saved	Check that at least two pods are selected and that you still have write access to every selected pod.

If the connection still fails, ask your administrator for help and include the network name, source and destination pod names, and the exact error message.