跳转到内容
#0169
WorkspacesTerminalContainers

One workspace, ten containers, one screen

The service runs across ten containers: three API workers, two background workers, a database, a cache, a scheduler, a metrics collector, an edge proxy. Operating it normally means ten ssh sessions, ten terminal apps, ten contexts to keep straight.

The team builds a workspace where each panel points at a different container's terminal URL. Ten panels, ten containers, all in one tab. The workspace doesn't care that the panels live on different containers: it just embeds each one as an iframe pointed at that container's terminal service.

The on-call engineer opens the workspace and sees ten live shells at once: all without an ssh agent, without a key, without a bastion.

Ten containers stop being ten places to ssh into and become ten panels in one tab.