Coder powers secure, scalable development across key industries — automotive, finance, government, and technology — enabling faster builds, tighter compliance, and seamless AI adoption in enterprise-grade cloud environments.
To stream Kubernetes events into your workspace startup logs, you can use
Coder's coder-logstream-kube
tool. coder-logstream-kube provides useful information about the workspace pod
or deployment, such as:
Causes of pod provisioning failures, or why a pod is stuck in a pending state.
Visibility into when pods are OOMKilled, or when they are evicted.
Prerequisites
coder-logstream-kube works best with the
kubernetes_deployment
Terraform resource, which requires the coder service account to have
permission to create deployments. For example, if you use
Helm to install Coder,
you should set coder.serviceAccount.enableDeployments=true in your
values.yaml
Here is an example of the logs you can expect to see in the workspace startup
logs:
Normal pod deployment
Wrong image
Kubernetes quota exceeded
Pod crash loop
How it works
Kubernetes provides an
informers API that streams pod
and event data from the API server.
coder-logstream-kube listens for pod creation events with containers that have
the CODER_AGENT_TOKEN environment variable set. All pod events are streamed as
logs to the Coder API using the agent token for authentication. For more
details, see the
coder-logstream-kube
repository.