k-logs

Tail k3s service logs by automating namespace and label lookups. The Skill runs kubectl get pods -A -l app=<service> to locate the pod, then executes kubectl logs -n <ns> -l <label>=<service> --tail=<lines> to fetch the output.

Yes, you can retrieve k3s logs on mobile. The Skill targets common k3s components such as traefik, grafana, prometheus, freshrss, uptime-kuma, and node-exporter, reducing manual kubectl syntax for mobile diagnostics.

When tailing k3s logs matches multiple pods, the Skill gracefully handles the situation by providing interleaved output. This expected behavior allows you to view concurrent log streams from all matching pods in a single retrieval.

You should not use this approach to tail k3s logs for host-Docker applications. The Skill provides clear guidance that it is specifically designed for k3s-hosted services managed within Kubernetes, not standalone Docker containers.

You do not need to manually specify complex parameters to fetch kubernetes logs. The Skill enables one-shot log retrieval with a configurable tail length, automatically injecting the --tail=<lines> argument into the kubectl logs command.

The best way to automate kubectl log retrieval for k3s components is using a Skill that resolves namespaces and labels automatically. It performs the pod lookup and log extraction in one shot, preventing manual syntax errors.