3
1
Fork
You've already forked coturn-chart
0

Feature: update chart to use single service instead of two #4

Open
opened 2026年05月14日 16:25:40 +02:00 by jessebot · 0 comments

Description of the change

TURNS cannot establish a connection over UDP, it requires TCP. The current chart creates two separate services:

  • One for UDP
  • One for TCP

This is unnecessary. Instead, a single Service can handle both protocols on the same ports. Here's what works:

apiVersion:v1kind:Servicemetadata:name:coturn-lbnamespace:coturnspec:type:LoadBalancerexternalTrafficPolicy:Localports:- name:turn-udpport:3478targetPort:3478protocol:UDP- name:turn-tcpport:3478targetPort:3478protocol:TCP- name:turn-tls-udpport:5349targetPort:5349protocol:UDP- name:turn-tls-tcpport:5349targetPort:5349protocol:TCPselector:app.kubernetes.io/name:coturn-coturnapp.kubernetes.io/instance:coturn

The chart should be updated to use a single service instead of two.

Benefits

avoids redundancy, and ensures TURNS works properly.

Possible drawbacks

Unsure.

Additional information

This was originally suggested in https://github.com/small-hack/coturn-chart/issues/110#issuecomment-2652207121 and ported here to codeberg.org since we're archiving the github.com repo.

## Description of the change TURNS cannot establish a connection over UDP, it requires TCP. The current chart creates two separate services: - One for UDP - One for TCP This is unnecessary. Instead, a single Service can handle both protocols on the same ports. Here's what works: ```yaml apiVersion: v1 kind: Service metadata: name: coturn-lb namespace: coturn spec: type: LoadBalancer externalTrafficPolicy: Local ports: - name: turn-udp port: 3478 targetPort: 3478 protocol: UDP - name: turn-tcp port: 3478 targetPort: 3478 protocol: TCP - name: turn-tls-udp port: 5349 targetPort: 5349 protocol: UDP - name: turn-tls-tcp port: 5349 targetPort: 5349 protocol: TCP selector: app.kubernetes.io/name: coturn-coturn app.kubernetes.io/instance: coturn ``` The chart should be updated to use a single service instead of two. ## Benefits avoids redundancy, and ensures TURNS works properly. ## Possible drawbacks Unsure. ## Additional information This was originally suggested in https://github.com/small-hack/coturn-chart/issues/110#issuecomment-2652207121 and ported here to codeberg.org since we're archiving the github.com repo.
Sign in to join this conversation.
No Branch/Tag specified
main
renovate/postgresql-18.x
renovate/mysql-14.x
9.8.0
9.7.1
9.6.0
9.5.2
9.5.1
9.5.0
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
open-engineering/coturn-chart#4
Reference in a new issue
open-engineering/coturn-chart
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?