Open roosterfish opened 1 year ago
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
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.
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.
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 thevalues.yml
file. Currently this is hardcoded toLocal
. Setting it toCluster
allows to make use of the traffic proxying feature between compute nodes of the cluster.Is there any reason this is currently hardcoded?
Thanks!