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

added externalTrafficPolicy to service #116

Merged
merged 1 commit into from
Dec 3, 2024

Conversation

koiralasandesh
Copy link
Contributor

When NodePort is used, plex container is unable to determine the user IP because k8s does NAT.
Because of this, all traffic seems to originate from the cluster itself.
This breaks a bunch of plex functionalities like determining bitrate for transcode and many other that rely on determining if the user is in LAN or WAN.
Setting externalTrafficPolicy: Local will allow Plex to determine the actual IP of user because this disables k8s NAT.
But this setting comes with caveats: the pods can only be accessed by the specific Node IP where the pod is running.

Read more here:
https://kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/#preserving-the-client-source-ip
https://access.redhat.com/solutions/7028639

This is my first time contributing, please let me know if there is specific branching requirements. I could not find any guidelines to contributing. Thanks!

@koiralasandesh koiralasandesh requested a review from a team as a code owner December 1, 2024 00:33
@cilindrox
Copy link
Member

Thanks @koiralasandesh !

@cilindrox cilindrox merged commit 61b6ed5 into plexinc:master Dec 3, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants