Secret_id_bound_cidr is not working if the vault is behind Load balancer


Vault cluster is running on Kubernetes cluster with nodeport service and fortend with load balance.
when we create a role with secret_id_bound_cidr it always get the source_adress of the overlay network deployed on the kubernetes cluster.
we have enabled X-Forwarded-For at load balance it vault get the source ip as overlay network IP.

Can you please help to resolve this setup.