You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current Kubernetes integration uses a NodePort to expose the ingress controller. I would like to use a Service of type LoadBalancer to leverage a VIP provided by MetalLB. However, when I configure the LoadBalancer service, the VIP's IP is forwarded instead of the actual client IP. Is there something I might be misconfiguring, or is this behavior expected and unavoidable in this setup?
Proposed solution (optional)
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Description
The current Kubernetes integration uses a NodePort to expose the ingress controller. I would like to use a Service of type LoadBalancer to leverage a VIP provided by MetalLB. However, when I configure the LoadBalancer service, the VIP's IP is forwarded instead of the actual client IP. Is there something I might be misconfiguring, or is this behavior expected and unavoidable in this setup?
Proposed solution (optional)
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: