Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
SlideShare a Scribd company logo

Troubleshooting Kubernetes

•
•
Sysdig
Sysdig

Kubernetes is a tremendous system for orchestrating your containers onto physical infrastructure. But troubleshooting Kubernetes can be incredibly challenging due to the dynamic and isolated nature of the containers it orchestrates. Sysdig leverages the powerful concept of container-aware system events and correlates each one of them with super rich metadata Kubernetes. In this session you’ll go deep into a couple of Kubernetes issues and how you would track them down using sysdig.

1 of 14
Troubleshooting Kubernetes Gianluca 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 theubiquitous 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!
Troubleshooting use 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!

More Related Content

Troubleshooting Kubernetes

  • 2. Information presented is confidential My ideal experience with containers
  • 3. Information presented is confidential My real experience with containers
  • 4. 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
  • 5. Information presented is confidential And troubleshooting is a real need! (https://github.com/kubernetes/kubernetes/issues/14051)
  • 6. Information presented is confidential Why sysdig sysdig is here to be theubiquitous debug tool to enhance your Kubernetes experience
  • 7. 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
  • 10. Information presented is confidential Services deep diving Kubernetes services are the best thing ever but… … do you really know how they work?!
  • 11. Information presented is confidential Frustrating timeouts Response time is arguably the most important metric... … let’s make sure it’s small enough!
  • 12. 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!
  • 13. 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