Ok,
Cool - I thought I could do it that way, just a bit worried it gets
forgotten when we resize / rebuild the nodes.
Thanks for the quick reply.
Cheers,
James
On Mon, May 21, 2018 at 8:05 PM, 'Ahmet Alp Balkan' via Kubernetes user
discussion and Q&A <kubernetes-users@googlegroups.com> wrote:
> This is not natively supported on GKE Ingress controller yet, so you can't
> specify it as part of your yaml manifest. But it is on the roadmap.
>
> In the meanwhile, to enable this on your Ingress:
>
> 1. Find your backend service name (it’s named like k8s-be-*):
>
> $ kubectl describe ingress helloweb | grep backends
>
> ingress.kubernetes.io/backends: {"k8s-be-31270--
> 87f51d5d53d5f570":"HEALTHY"}
>
>
> 2.Add user-defined request headers to this backend, as specified in the
> doc you linked:
>
> gcloud beta compute backend-services update \
> --global k8s-be-31270--87f51d5d53d5f570 \
> --custom-request-header 'X-Client-Geo-City:{client_city},{client_region}'
> \
> --custom-request-header 'X-Client-Geo-Coordinates:{
> client_city_lat_long}'
>
>
> On Mon, May 21, 2018 at 9:05 AM <jmbr...@gmail.com> wrote:
>
>> Afternoon,
>>
>> I saw this article the other day https://blog.doit-intl.com/
>> farewell-maxmind-geolocating-requests-with-google-load-
>> balancer-for-free-7938f5adbef0 describes how it is possible to configure
>> the Googel load balancers to pass the location of the ip address to the
>> compute instance.
>>
>> Does anyone know if this supported by Kubernetes yet? I imagine I can
>> setup the compute instance directly but ideally I would like to tweak my
>> ingress with the info (or have it on by default) for when we update.
>>
>> Any pointers would be super handy.
>>
>> Cheers,
>> James
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Kubernetes user discussion and Q&A" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to kubernetes-users+unsubscr...@googlegroups.com.
>> To post to this group, send email to kubernetes-users@googlegroups.com.
>> Visit this group at https://groups.google.com/group/kubernetes-users.
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Kubernetes user discussion and Q&A" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/kubernetes-users/kur70lxi69Q/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> kubernetes-users+unsubscr...@googlegroups.com.
> To post to this group, send email to kubernetes-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/kubernetes-users.
> For more options, visit https://groups.google.com/d/optout.
>
--
You received this message because you are subscribed to the Google Groups
"Kubernetes user discussion and Q&A" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to kubernetes-users+unsubscr...@googlegroups.com.
To post to this group, send email to kubernetes-users@googlegroups.com.
Visit this group at https://groups.google.com/group/kubernetes-users.
For more options, visit https://groups.google.com/d/optout.
