Gitpod Workspace Log Access vs. Deployment Pod Logs Integration Boundary

Gitpod workspaces execute inside a Kubernetes pod that hosts a Docker daemon, separating the IDE container logs from any sidecar container logs used by the deployment.

The UI’s ‘Pod Logs’ view aggregates only the primary workspace container logs, while deployment logs from sidecar containers remain inaccessible without additional configuration, and the documentation does not define a standard method for persisting or forwarding these logs, creating uncertainty around log aggregation choices and RBAC‑based access restrictions.

How can users reliably retrieve deployment logs from sidecar containers within a Gitpod workspace? What is the recommended approach for persisting such logs across workspace recycling events? Is there a documented method to expose sidecar logs through the existing Gitpod log collection pipeline?