Kubetap - kubectl plugin to interactively proxy Kubernetes Services with ease
On Thursday I released a new open source project, kubetap, a kubectl plugin to interactively proxy Kubernetes Services. Currently only HTTP (via mitmproxy) is implemented, but other tap types are planned for the future, such as TCP/UDP and gRPC.
This tool was created because I needed to inspect and manipulate traffic destined for microservices deep with a technology stack. Alternatives, such as solo's Squash or telepresence were far too heavy handed for the task at hand. I hope that kubetap will be useful for developers and security auditors alike.
Code repo is here: https://github.com/soluble-ai/kubetap
Project site here: https://soluble-ai.github.io/kubetap/
If you have any issues, please feel free to open a GitHub ticket.
19 comments · 88% upvoted · other discussions
I'm still not sure I understand. Can you describe the ideal use case for this? Who's this for, why would they want it, and why is it better than existing solutions?
Better still if you can persuade people in an introduction in the documentation.
Eriner_ [OP] 1 points · May 2020
Please check the project site - I have a video and cover use cases in the introduction page.
otterley 0 points · May 2020
I did - and I think it could use more explanation. Videos are great, but someone with less time should be able to understand by reading a couple of well written paragraphs.
Eriner_ [OP] 1 points · May 2020
I created a written documentation of the use cases on the front page of the project site. There are pictures, but it is in fact only a few paragraphs :)
If you think something is missing, please let me know precisely what is not in the docs and I'll be happy to add it.
otterley 2 points · May 2020
I was referring to the repo’s README file as opposed to the website. Sorry about the confusion. The project site is pretty good.
Eriner_ [OP] 1 points · May 2020
Should I add something to the README to funnel people to the project site more? I feel like there are already enough links to it, but I want to make sure others don't have the same poor initial experience you did. That said, I also don't want to duplicate the entire doc site into the README.