Skip to content
Deep kubernetes visibility from the kubectl
Branch: develop
Clone or download
leodido and fntlnz fix(pkg/digjob): fine-grained volumes (#4)
Co-authored-by: Lorenzo Fontana <>
Signed-off-by: Leonardo Di Donato <>
Latest commit 17316b5 May 31, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
cmd/kubectl-dig new: moving to sysdiglabs organization May 21, 2019
docs docs: banner image May 21, 2019
pkg fix(pkg/digjob): fine-grained volumes (#4) May 31, 2019
vendor deps: vendor May 20, 2019
.gitignore new: gitignore May 20, 2019
Makefile new: moving to sysdiglabs organization May 21, 2019 docs: project status May 21, 2019
go.mod new: moving to sysdiglabs organization May 21, 2019
go.sum deps: modules May 20, 2019

kubectl dig

Deep kubernetes visibility from the kubectl.

kubectl dig logo kubectl dig
A simple, intuitive, and fully customizable UI to dig into your kubernetes clusters
kubectl dig <node>



go get -u


Just dig

There's only one thing to do, provide the node name!

kubectl dig <node>

You just identify the node you want to dig in with kubectl get nodes and then provide it to the dig command!

kubectl dig ip-180-12-0-152.ec2.internal

dig + cluster metadata

By default, kubectl dig shows only information about the local node, if you want to dig from that node to the whole cluster you have to provide a service account that can read resources.

You can create a dig-viewer service account with:

kubectl apply -f

Then you just use it with kubectl dig.

kubectl dig --serviceaccount dig-viewer

At this point you have access to the fancy cluster metadata, press F2 and look for the K8s views!

Project status

High-level todo

  • Basic functionalities;
  • Finish all the planned commands;
  • Merge here the functionalities of kubectl-capture;
  • Integration tests;
  • Errors detection on the kernel module;

Planned commands

  • run command, to execute digs;
  • list command, to list all the executed digs;
  • attach command, to attach to an existing dig that was previously detached;
  • delete command, to delete an existing dig;
  • where command, to execute digs where the chosen workloads are, instead of having to specify the node directly;


You can’t perform that action at this time.