simple-server | simple server node | Runtime Evironment library

You should use rtsp_simple_server:8554 instead of localhost.

Since in the container called rtsp_streaming, localhost means rtsp_streaming and in rtsp_simple_server, localhost means rtsp_simple_server`. So you should use the container's name.

Make sure that in your Cargo.toml name = "test_project". Also, you can only import it if it is a library Library Documentation.

Looking at your Cargo.toml, the lib section tells cargo that this package exports one lib called errormsg contained in errormsg/src/lib.rs. So test_project will not be available for you, because only one lib is allowed per package why?.

There are two solutions to your problem.
You can either make errormsg a module which you then can import for example with test_project::errormsg in tests/users.rs.
Or you can create a separate package and then import it in the Cargo.toml file:

When you say, "the quality of the video becomes pretty bad," I guess you mean your transcoded output video has a lot of block artifacts in it. That's generally because you haven't allocated enough bandwidth to your output video stream. Without enough output bandwidth to play with, the coder quantizes and eliminates higher-frequency stuff so it looks nasty.

You didn't mention what sort of program material you have. But it's worth mentioning this: in material with lots of motion (think James Bond flick) it doesn't save much bandwidth to reduce the frame rate: we're coding the difference between successive frames. The longer you wait between frames, the more differences there are to code (and the harder the motion estimator has to work). If you radically reduce the frame rate (from 24 to 2 for example) it gets much worse.

Talking-heads material is generally less sensitive to framerate.

You might try setting your bandwidth -- your output bitrate -- explicitly like this.

HAProxy by default allows to reuse the same port number across the same or other frontend/listen sections and also across other haproxy process. This can be changed adding noreuseport in the global section.

The default HAProxy Ingress configuration uses port number 1936 to expose stats. If such port number is reused by eg a tcp proxy, the incoming requests will be distributed between both frontends - sometimes your service will be called, sometimes the stats page. Changing the tcp proxy or the stats page (doc here) to another port should solve the issue.

Combined command:

The native GKE ingress controller does not support ClusterIP, but it works perfectly with LoadBalancer and NodePort type. Take a look at this issue

Non-native ingress controller Nginx works with ClusterIP.

I solved it the strange way. I created a controller I named AuthController and added these methods to it