Troubleshooting KubernetesGianluca Borello, Engineering Manager

Information presented is confidential

My ideal experience with containers

Information presented is confidential

My real experience with containers

Information presented is confidential

Kubernetes to the rescue

Kubernetes is a remarkable transition towards the ideal experience…

...but it doesn’t help much with troubleshooting, a container is still:

• Isolated

• Not context-aware

• Minimal runtime

• Moving around

Information presented is confidential

And troubleshooting is a real need!

(https://github.com/kubernetes/kubernetes/issues/14051)

Information presented is confidential

Why sysdig

sysdig is here to be the ubiquitous debug

tool to enhance your Kubernetes experience

Information presented is confidential

Why sysdig

What’s so special about sysdig + Kubernetes?

sysdig leverages the powerful concept of container-aware

system events and correlates each one of them with super rich

metadata coming from the Kubernetes API server

Sysdig demo!

Troubleshootinguse cases

Information presented is confidential

Services deep diving

Kubernetes services are the best thing ever but…

… do you really know how they work?!

Information presented is confidential

Frustrating timeouts

Response time is arguably the most important metric...

… let’s make sure it’s small enough!

Information presented is confidential

A rolling deployment gone wrong

Rolling updates are the basic building block for achieving

zero downtime deployments…

… except when they betray you!

Information presented is confidential

More troubleshooting stories

Read our blog posts:

• https://sysdig.com/blog/sysdigkubernetes-adventure-part-1-kubernetes-s

ervices-work/

• https://sysdig.com/blog/a-sysdigkubernetes-adventure-part-2-troublesho

oting-kubernetes-services

• https://sysdig.com/blog/digging-into-kubernetes-with-sysdig

Thank You!