kubesess VS inspektor-gadget

You can find it here: kubesess

I wrote a similar tool in rust! Super happy with it kubesess!

If you don’t have a local cluster, you could always bypass Argo and deploy straight to dev cluster, just turn off auto deploy first. I use my own tool to navigate clusters (kubesess

I’ve created a tool, kubesess, that does just that! I use it myself daily, it’s super fast, some would say BLAZINGLY FAST program written I rust.

You should take a look into kubesess. I wrote it because I wanted a fast and lightweight way of doing context per session

I am also the author of another cli tool called kubesess that helps with session-based contexts.

You can find it here: Ramilito/kubesess: Kubectl plugin managing sessions (github.com)

kubesess (repo) is a tool for handling contexts in kubernetes and shines when you have many contexts!

You can try using https://www.inspektor-gadget.io/ You can try either, top tcp, trace network-graph or trace tcp gadget. It's a CNCF sandbox project and it's kubernetes native so I think this should work.

This works really well https://github.com/inspektor-gadget/inspektor-gadget/blob/main/docs/gadgets/advise/network-policy.md

Link to GitHub Repository

Inspector gadget is a tool designed to introspect and debug Kubernetes applications using eBPF.

I found this tool: https://github.com/kinvolk/inspektor-gadget great if you want to have a detailed debugging for running pods e.g all exec system calls or trace tcp connections etc.

All namespaces should have NetworkPolicy. Interactions between namespaces should be limited to NetworkPolicy following least privileges principles (Inspektor Gadget)

The team behind traceloop has integrated it with the Inspektor Gadget project, so you can run traceloop on the K8s platform using kubectl. See the demos in Inspektor Gadget - How to use and, if you like, try it on your own.