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

Feature: Add support for multiple users declaritively #1

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

I'd like to support adding more than one user to match what is possible in the coturn/coturn:examples/etc/turnserver.conf

We should probably convert this into an array: github.com/jessebot/coturn-chart@8650cf1ce7/charts/coturn/values.yaml (L128-L140)

The array in the values.yaml could look like this:

# most coturn config parameters that you really needcoturn:users:- username:password:secretKeys:username:usernamepassword:password

The question is how do we handle this securely? Right now, these values get passed into a secret, to avoid having plain text passwords, like this: github.com/jessebot/coturn-chart@8650cf1ce7/charts/coturn/templates/auth-secret.yaml (L8-L14)

And then they're passed into an init container in the deployment via an env var here: github.com/jessebot/coturn-chart@8650cf1ce7/charts/coturn/templates/deployment.yaml (L57-L74)

So they can then be concatenated in via yq here: github.com/jessebot/coturn-chart@8650cf1ce7/charts/coturn/templates/deployment.yaml (L119)

The issue is I don't know what to do here for the init container. I guess we can just make the secret more complex, or we could change the init container to possibly add the users via actual turnserver cli commands? 🤔 I'm open to suggestions and PRs.

I'd like to support adding more than one user to match what is possible in the [coturn/coturn:`examples/etc/turnserver.conf`](https://github.com/coturn/coturn/blob/d7db17f048675f46fc2b30827813eeaf0c822fb2/examples/etc/turnserver.conf#L256-L280) We should probably convert this into an array: https://github.com/jessebot/coturn-chart/blob/8650cf1ce74ec2a2dc5a720235779c58fb9eefe2/charts/coturn/values.yaml#L128-L140 The array in the values.yaml could look like this: ```yaml # most coturn config parameters that you really need coturn: users: - username: password: secretKeys: username: username password: password ``` The question is how do we handle this securely? Right now, these values get passed into a secret, to avoid having plain text passwords, like this: https://github.com/jessebot/coturn-chart/blob/8650cf1ce74ec2a2dc5a720235779c58fb9eefe2/charts/coturn/templates/auth-secret.yaml#L8-L14 And then they're passed into an init container in the deployment via an env var here: https://github.com/jessebot/coturn-chart/blob/8650cf1ce74ec2a2dc5a720235779c58fb9eefe2/charts/coturn/templates/deployment.yaml#L57-L74 So they can then be concatenated in via [`yq`](https://github.com/mikefarah/yq) here: https://github.com/jessebot/coturn-chart/blob/8650cf1ce74ec2a2dc5a720235779c58fb9eefe2/charts/coturn/templates/deployment.yaml#L119 The issue is I don't know what to do here for the init container. I guess we can just make the secret more complex, or we could change the init container to possibly add the users via actual turnserver cli commands? 🤔 I'm open to suggestions and PRs.
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#1
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?