User Story
As a platform operator running an agent as the sandbox command (spec.command),
I want that agent’s stdout and stderr to appear in the sandbox pod’s Kubernetes logs,
so that I can operate and debug the agent the same way as any other container.
Problem Statement
When a sandbox is created with an agent command, the agent runs and writes logs to stdout and stderr. Those lines do not appear in kubectl logs for the sandbox container. Only OpenShell supervisor messages appear. A simple print to stdout from the same agent process is also missing.
Impact / Why This Matters
Operators cannot see agent logs from the container log stream. They have to start the agent again through an exec session to see output, and that output is only on that session — not in the container log, and not what the platform uses to run the agent. This blocks normal log collection, alerting, and support.
Acceptance Criteria
After CreateSandbox with spec.command set to an agent that writes to stdout, those lines appear in kubectl logs on the sandbox container..
Reproduction Steps
Deploy OpenShell on Kubernetes with the Kubernetes compute driver.
Create a sandbox whose command is an application that prints to stdout (for example a line every few seconds, plus normal application logs).
Wait until the sandbox is ready and the command is running.
Run kubectl logs on the sandbox pod / agent container.
Observe that only supervisor messages appear; the application’s stdout lines do not.
Environment
OpenShell Helm chart: 0.1.2-patch.1
OpenShell gateway image: 0.1.2
OpenShell supervisor image: 0.1.2
OpenShell sandbox base image: 0.1.2
Kubernetes Agent Sandbox controller: v1.0.2
Runtime: Kubernetes (OpenShift)
Deployment: Kubernetes driver, sandbox created via CreateSandbox / spec.command
Logs
User Story
As a platform operator running an agent as the sandbox command (spec.command),
I want that agent’s stdout and stderr to appear in the sandbox pod’s Kubernetes logs,
so that I can operate and debug the agent the same way as any other container.
Problem Statement
When a sandbox is created with an agent command, the agent runs and writes logs to stdout and stderr. Those lines do not appear in kubectl logs for the sandbox container. Only OpenShell supervisor messages appear. A simple print to stdout from the same agent process is also missing.
Impact / Why This Matters
Operators cannot see agent logs from the container log stream. They have to start the agent again through an exec session to see output, and that output is only on that session — not in the container log, and not what the platform uses to run the agent. This blocks normal log collection, alerting, and support.
Acceptance Criteria
After CreateSandbox with spec.command set to an agent that writes to stdout, those lines appear in kubectl logs on the sandbox container..
Reproduction Steps
Deploy OpenShell on Kubernetes with the Kubernetes compute driver.
Create a sandbox whose command is an application that prints to stdout (for example a line every few seconds, plus normal application logs).
Wait until the sandbox is ready and the command is running.
Run kubectl logs on the sandbox pod / agent container.
Observe that only supervisor messages appear; the application’s stdout lines do not.
Environment
OpenShell Helm chart: 0.1.2-patch.1
OpenShell gateway image: 0.1.2
OpenShell supervisor image: 0.1.2
OpenShell sandbox base image: 0.1.2
Kubernetes Agent Sandbox controller: v1.0.2
Runtime: Kubernetes (OpenShift)
Deployment: Kubernetes driver, sandbox created via CreateSandbox / spec.command
Logs