Read your service’s logs without a production kubeconfig
Scoped log access: your namespaces, your pods, nobody else’s.
“Can you paste me the last 200 lines from checkout-api in prod? Trying to work out if it is our timeout or theirs”
What the wait costs
Debugging by proxy: every follow-up question costs another round trip through someone else’s terminal.
In Fenwave
Kubernetes›prod-eu-west-1›checkout-api›Logs
Capability
Kubernetes AdminThe reason developers are not given production log access is usually not the logs — it is that the only mechanism available hands over a kubeconfig that can also delete a StatefulSet. Fenwave separates reading from doing. A developer sees pods, events, restart history and streaming logs for the services their team owns, and sees nothing else, because the same role model governs this screen as governs everything else in the platform.
How it works
- 01Open Kubernetes and pick the cluster and namespace you have access to.
- 02Select the pod; state, restart count and resource usage are on the same view.
- 03Stream the logs live, or scroll back through the buffer.
- 04Events and quota limits sit beside the logs, where the cause often is.