Skip to content
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

I used lb. Let's talk about it #136

Open
hudson-s opened this issue Oct 23, 2024 · 0 comments
Open

I used lb. Let's talk about it #136

hudson-s opened this issue Oct 23, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@hudson-s
Copy link

hudson-s commented Oct 23, 2024

My values.yaml are as follows

service:
  # -- The type of service to deploy for routing Coturn traffic.
  #   ClusterIP: Recommended for DaemonSet configurations. This will create a
  #              standard Kubernetes service for Coturn within the cluster.
  #              No external networking will be configured as the DaemonSet
  #              will handle binding to each Node's host networking
  #
  #   NodePort:  Recommended for Deployment configurations. This will open
  #              TURN ports on every node and route traffic on these ports to
  #              the Coturn pods. You will need to make sure your cloud
  #              provider supports the cluster config setting,
  #              apiserver.service-node-port-range, as this range must contain
  #              the ports defined above for the service to be created.
  #
  #   LoadBalancer: This was what was originally set for this chart in the
  #                 upstream of this fork, but with no details
 
  type: LoadBalancer
 
  externalTrafficPolicy: "Local"

image

During my deployment with this project, I found that no turn public ip was leaked. So I switched to lb. How did you leak the public ip address?

Sudden leakage after the public IP test turn can use https://webrtc.github.io/samples/src/content/peerconnection/trickle-ice/ server is running

@hudson-s hudson-s added the enhancement New feature or request label Oct 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant