-
Notifications
You must be signed in to change notification settings - Fork 39
Set ipFamilyPolicy on RTC SFU NodePorts #660
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
base: main
Are you sure you want to change the base?
Conversation
If the cluster is IPv6 enabled [1], NodePorts created for RTC SFU will still default to SingleStack. Set ipFamilyPolicy on these ports to PreferDualStack instead so we can connect with both IPv4 and v6. This should cause no change in behavior on an IPv4-only install. [1] https://docs.k3s.io/networking/basic-network-options#dual-stack-ipv4--ipv6-networking
dyff of changes in rendered templates of CI manifestsFull contents of manifests and dyffs are available in https://github.com/element-hq/ess-helm/actions/runs/16876490201/artifacts/3733019933 matrix-rtc-checkov-values.yaml@@ Service/ess-ci/release-name-matrix-rtc-sfu-muxed-udp - spec @@
+ ipFamilyPolicy: PreferDualStack
@@ Service/ess-ci/release-name-matrix-rtc-sfu-tcp - spec @@
+ ipFamilyPolicy: PreferDualStack
matrix-rtc-exposed-services-values.yaml@@ Service/ess-ci/release-name-matrix-rtc-sfu-muxed-udp - spec @@
+ ipFamilyPolicy: PreferDualStack
@@ Service/ess-ci/release-name-matrix-rtc-sfu-tcp - spec @@
+ ipFamilyPolicy: PreferDualStack
@@ Service/ess-ci/release-name-matrix-rtc-sfu-udp-range-0 - spec @@
+ ipFamilyPolicy: PreferDualStack
@@ Service/ess-ci/release-name-matrix-rtc-sfu-udp-range-1 - spec @@
+ ipFamilyPolicy: PreferDualStack
matrix-rtc-minimal-values.yaml@@ Service/ess-ci/release-name-matrix-rtc-sfu-muxed-udp - spec @@
+ ipFamilyPolicy: PreferDualStack
@@ Service/ess-ci/release-name-matrix-rtc-sfu-tcp - spec @@
+ ipFamilyPolicy: PreferDualStack
matrix-rtc-secrets-externally-values.yaml@@ Service/ess-ci/release-name-matrix-rtc-sfu-muxed-udp - spec @@
+ ipFamilyPolicy: PreferDualStack
@@ Service/ess-ci/release-name-matrix-rtc-sfu-tcp - spec @@
+ ipFamilyPolicy: PreferDualStack
matrix-rtc-secrets-in-helm-values.yaml@@ Service/ess-ci/release-name-matrix-rtc-sfu-muxed-udp - spec @@
+ ipFamilyPolicy: PreferDualStack
@@ Service/ess-ci/release-name-matrix-rtc-sfu-tcp - spec @@
+ ipFamilyPolicy: PreferDualStack
pytest-matrix-rtc-standalone-values.yaml@@ Service/ess-ci/release-name-matrix-rtc-sfu-muxed-udp - spec @@
+ ipFamilyPolicy: PreferDualStack
@@ Service/ess-ci/release-name-matrix-rtc-sfu-tcp - spec @@
+ ipFamilyPolicy: PreferDualStack
pytest-matrix-rtc-synapse-wellknown-values.yaml@@ Service/ess-ci/release-name-matrix-rtc-sfu-muxed-udp - spec @@
+ ipFamilyPolicy: PreferDualStack
@@ Service/ess-ci/release-name-matrix-rtc-sfu-tcp - spec @@
+ ipFamilyPolicy: PreferDualStack
quick-setup-certificates-pg-external-values.yaml@@ Service/ess-ci/release-name-matrix-rtc-sfu-muxed-udp - spec @@
+ ipFamilyPolicy: PreferDualStack
@@ Service/ess-ci/release-name-matrix-rtc-sfu-tcp - spec @@
+ ipFamilyPolicy: PreferDualStack
quick-setup-certificates-pg-with-helm-values.yaml@@ Service/ess-ci/release-name-matrix-rtc-sfu-muxed-udp - spec @@
+ ipFamilyPolicy: PreferDualStack
@@ Service/ess-ci/release-name-matrix-rtc-sfu-tcp - spec @@
+ ipFamilyPolicy: PreferDualStack
quick-setup-external-cert-pg-external-values.yaml@@ Service/ess-ci/release-name-matrix-rtc-sfu-muxed-udp - spec @@
+ ipFamilyPolicy: PreferDualStack
@@ Service/ess-ci/release-name-matrix-rtc-sfu-tcp - spec @@
+ ipFamilyPolicy: PreferDualStack
quick-setup-external-cert-pg-with-helm-values.yaml@@ Service/ess-ci/release-name-matrix-rtc-sfu-muxed-udp - spec @@
+ ipFamilyPolicy: PreferDualStack
@@ Service/ess-ci/release-name-matrix-rtc-sfu-tcp - spec @@
+ ipFamilyPolicy: PreferDualStack
quick-setup-letsencrypt-pg-external-values.yaml@@ Service/ess-ci/release-name-matrix-rtc-sfu-muxed-udp - spec @@
+ ipFamilyPolicy: PreferDualStack
@@ Service/ess-ci/release-name-matrix-rtc-sfu-tcp - spec @@
+ ipFamilyPolicy: PreferDualStack
quick-setup-letsencrypt-pg-with-helm-values.yaml@@ Service/ess-ci/release-name-matrix-rtc-sfu-muxed-udp - spec @@
+ ipFamilyPolicy: PreferDualStack
@@ Service/ess-ci/release-name-matrix-rtc-sfu-tcp - spec @@
+ ipFamilyPolicy: PreferDualStack
quick-setup-wildcard-cert-pg-external-values.yaml@@ Service/ess-ci/release-name-matrix-rtc-sfu-muxed-udp - spec @@
+ ipFamilyPolicy: PreferDualStack
@@ Service/ess-ci/release-name-matrix-rtc-sfu-tcp - spec @@
+ ipFamilyPolicy: PreferDualStack
quick-setup-wildcard-cert-pg-with-helm-values.yaml@@ Service/ess-ci/release-name-matrix-rtc-sfu-muxed-udp - spec @@
+ ipFamilyPolicy: PreferDualStack
@@ Service/ess-ci/release-name-matrix-rtc-sfu-tcp - spec @@
+ ipFamilyPolicy: PreferDualStack
|
Thanks for this contribution. Some notes / thoughts
|
Sorry for closing the PR, linking the PRs made github think it should close it. |
I think it only matters for ports that get exposed outside the cluster. Other than the RTC ports I'm enabling in this PR, this chart only exposes http/https via traefik LoadBalancer ingress, and those seem to listen to IPv6 automatically when I enabled it.
I don't think so. There are only a few options for this resource:
I don't see why someone would pick one of others. |
If the cluster is IPv6 enabled, NodePorts created for RTC SFU will still default to SingleStack. Set ipFamilyPolicy on these ports to PreferDualStack instead so we can connect with both IPv4 and v6.
This should cause no change in behavior on an IPv4-only install.