Is this project maintained?

[russell]

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.

[jiriks74]

Sadly I'd say that this is pretty much dead. It even has issues starting the mitmproxy container as the container never reaches the ready state. For it to do this I had to patch out the readiness probe, add tty: true to the config and then pass mitmweb --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]

So the project had issues with things like LoadBalancerClass which I was able to solve by updating the k8s API modules. It seems like getting this into a useful state wouldn't be that insane of an idea.

[jiriks74]

Another update: I was able to fix the config.yml issue where it didn't load with mitmproxy/mitmproxy:latest and by that I removed the need for a custom container. I also set the default image to the upstream mitmproxy/mitmproxy:latest image

So 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'