-
-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Specifying the LoadBalancer #50
Comments
Hi! Which type of LB do you use? Klipper or Hetzner LB? Are there any other logs available? Klipper should use host ports and stunner fallbacks to nodePort if LB service cannot be created. So it shall work with Klipper. |
I use Hetzner LB. |
My understanding is I need to customize LB settings for The Gateway resource.
Any chance I can create the LB using those configurations? |
Great to hear that it became healthy! I would need to check the stunner config to be able to figure out what happens now. Stunner supports TCP afaik, but it is useless for media. Could you share the content of the stunnerd configmap? You can contact me on Discord if its confidential. Btw, may I ask why don't you just switch LB? |
Can we confirm if this is the case? Because I do stream a media. Which won't be the best experience using TCP.
To be honest, I would love to :)
I would love to catch-up on Discord. How can I find you? |
Hey @Biacode! You can join here: https://discord.gg/DyPgEsbwzc |
I agree, this is definitely a "RTP over TCP sux" issue. Nevertheless, I find that most of the time TCP can still provide a decent media experience unless the Internet connection is extremely poor, can it be the case that there is a crowded Wifi or a 3G mobile uplink somewhere in the media path?
You can set the annotations you want STUNner to add to the LB services it creates in the GatewayConfig If we are at it, can you share a few words about your use case? We'd be delighted to learn how/why you find STUNner useful in your WebRTC endeavors (if at all...:-)). |
No, nothing like crowded wifi or 3G mobile. My use case works perfectly fine with a UDP or let's say non K8S setup.
That helps. Thanks. I guess I will stop using stunner since TCP is not my solution.
I need to stream/capture desktop content in real-time. |
Can this happen because of no UDP support in Hetzner LB? hetznercloud/hcloud-cloud-controller-manager#252 (comment) It looks like the automation tool supports klipper, which should work with UDP. AFAIK, our neko example was originally done with klipper (and k3s). |
Thank you, @levaitamas. I appreciate your efforts on trying to help. |
Hi @Biacode, the newest STUNner point release supports HTTP health checking, does this solve your problem? Sorry, no testbed here, that's why I'm asking. Also, the NodePort fallback is always available if you don't like the LB your provider offers. At the moment you cannot prevent STUNner from creating an LB, but once we fix this issue you will be able to override this default. |
Closing this issue due to inactivity. Feel free to reopen if the problem persists. |
Hello,
Sorry for the dumb question, but Is there a way to specify the LoadBalancer instead of creating a new one?
Or perhaps it is better if I describe my issue.
I use the Hetzner cloud with this automation tool to deploy the k8s cluster.
Whenever I deploy the stunner UDPRoute, it creates a new LB, which never gets to a healthy state. See the screenshot below.
Happy to learn how I can deal with this issue.
The text was updated successfully, but these errors were encountered: