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

Helm Chart Service externalTrafficPolicy #2011

Open
roosterfish opened this issue Mar 1, 2023 · 3 comments
Open

Helm Chart Service externalTrafficPolicy #2011

roosterfish opened this issue Mar 1, 2023 · 3 comments
Assignees
Labels
enhancement New feature or request Environment Issue and bug related to environment

Comments

@roosterfish
Copy link

Hi,

When trying to use the Helm chart with a Service of type NodePort, it would be beneficial being able to set the externalTrafficPolicy setting through the values.yml file. Currently this is hardcoded to Local. Setting it to Cluster allows to make use of the traffic proxying feature between compute nodes of the cluster.

Is there any reason this is currently hardcoded?

Thanks!

@rjha-splunk
Copy link
Collaborator

Hi,

Thanks for raising it , we will take this and review in our upcoming sprint.

The values.yaml is still evolving , when we see a chance we improve it.

Regards,
Rahul

@rjha-splunk rjha-splunk added enhancement New feature or request Environment Issue and bug related to environment labels Mar 1, 2023
@ehlo550
Copy link
Contributor

ehlo550 commented Mar 8, 2023

Hi,
From my point of view this is hardcoded to local as you would loose the original source IP of the logs when using Cluster.

@roosterfish
Copy link
Author

Hi @ehlo550, you will indeed loose the IP information, if the traffic doesn't hit a pod on the same compute node you are connecting to. However having this configurable wouldn't require putting an additional LB in front (e.g. if MetalLB is not an option) since the cluster will take care about distributing the incoming traffic to active pods all over the cluster.

@rjha-splunk rjha-splunk self-assigned this Jul 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Environment Issue and bug related to environment
Projects
None yet
Development

No branches or pull requests

3 participants