-
Notifications
You must be signed in to change notification settings - Fork 54
Open
Description
Description
It has been 3 years since there has been any activity on this project? Would it be possible to move this out to it's own organisation so that volunteers can take over stewardship?
I'm the author of the tiny patch #16 but I think that it wouldn't be hard to find a few more people to help out. Seems there are still being bugs lodged against the project so there is still community interest in it.
sym-stiller, tanvp112, nnWhisperer, danielloader, leonid-leshukov and 4 more
Activity
jiriks74 commentedon Mar 31, 2025
Sadly I'd say that this is pretty much dead. It even has issues starting the
mitmproxy
container as the container never reaches theready
state. For it to do this I had to patch out the readiness probe, addtty: true
to the config and then passmitmweb --web-port 2244 --web-host 0.0.0.0 --listen-port 7777
arguments just so that it would start and detect the container and route the ports.I may look into making this run later on but I am in no shape to take on the development of this. I don't know
go
and I'm new with k8s. If I manage to get it running I'll post my findings and probably make a patched repo but I'm not sure I'll be able to keep this working without help.jiriks74 commentedon Apr 1, 2025
So the project had issues with things like
LoadBalancerClass
which I was able to solve by updating thek8s
API modules. It seems like getting this into a useful state wouldn't be that insane of an idea.jiriks74 commentedon Apr 2, 2025
Another update: I was able to fix the
config.yml
issue where it didn't load withmitmproxy/mitmproxy:latest
and by that I removed the need for a custom container. I also set the default image to the upstreammitmproxy/mitmproxy:latest
imageSo I have a proof of concept that is able to run without any custom configuration:
kubectl-tap on -n default loadbalancer-service -p 80 --protocol reverse --browser'