-
Notifications
You must be signed in to change notification settings - Fork 325
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
coturn: Add IP configuration options #4083
Conversation
# If you need to specify which IP Coturn should bind to. | ||
# This will typically be the IP of the kubenode. | ||
# coturnTurnListenIP: "182.168.22.133" | ||
# coturnTurnListenIP: "1.2.3.4" # can also be __COTURN_EXT_IP__, __COTURN_POD_IP__,__COTURN_HOST_IP__ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some comment explaining the difference between ...ListenIp
, ...RelayIp
and ...ExternalIp
would be helpful.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wouldn't that just reproduce the docs fo coturn?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, but IMHO otherwise admins would need to understand coturn
itself and not just look at our Helm charts. 🤔
This PR adds configuration options in the
coturn
helm chart for settingsrelay-ip
external-ip
prometheus-ip
federation-listening-ip
It also adds a
__COTURN_HOST_IP__
template variable which will be substitued by the host ip of thek8s
node that is running coturn.This PR is backwards-compatible to
values.yaml
files written for version of this helm charts without this PR: new variables have defaults that match their previous hardcoded value.Checklist
changelog.d