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

coturn: Add IP configuration options #4083

Merged
merged 4 commits into from
Jun 21, 2024
Merged

Conversation

smatting
Copy link
Contributor

@smatting smatting commented Jun 5, 2024

This PR adds configuration options in the coturn helm chart for settings

  • relay-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 the k8s 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

  • Add a new entry in an appropriate subdirectory of changelog.d
  • Read and follow the PR guidelines

@zebot zebot added the ok-to-test Approved for running tests in CI, overrides not-ok-to-test if both labels exist label Jun 5, 2024
@smatting smatting changed the title coturn: add ip configuration options coturn: Add IP configuration options Jun 13, 2024
@smatting smatting marked this pull request as ready for review June 13, 2024 14:55
# 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__
Copy link
Contributor

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.

Copy link
Contributor Author

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?

Copy link
Contributor

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. 🤔

@smatting smatting merged commit 48d0d8e into develop Jun 21, 2024
9 checks passed
@smatting smatting deleted the WPB-9130-coturn-host-ip branch June 21, 2024 12:34
smatting added a commit that referenced this pull request Jun 25, 2024
@echoes-hq echoes-hq bot added the echoes: product-roadmap Work aligned with the customer-announced roadmap, targeting a specific release date. label Jun 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
echoes: product-roadmap Work aligned with the customer-announced roadmap, targeting a specific release date. ok-to-test Approved for running tests in CI, overrides not-ok-to-test if both labels exist
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants