-
Notifications
You must be signed in to change notification settings - Fork 93
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
GeoIP strategy #1182
Comments
Let me try to summon our geoip strategy creator/guru :) @k0da do you see anything obvious here? |
Could you please paste your dnsenpoint objects from application namespace? |
Hey, I'm trying to use the geoip strategy with K8GB, but I'm finding some issues.
So far, this is what I've got. I created two different GslB objects, one with round robin strategy and the other with geoip strategy
When running
dig @10.171.61.137 -p 30053 liqo.cloud.testanim.com +subnet=10.10.72.146
I get what I'm expectingWhere the ips
10.233.46.163, 10.171.61.252, 10.181.61.250
are ingress load balancers in different clusters (adc, edc, stg).However, when querying the geoip host
dig @10.171.61.137 -p 30053 liqogeoip.cloud.testanim.com +subnet=10.10.72.146
I get the same ipsThis is the script I used to create my geoip db
Note that the CIDR range "10.10.0.0/16" (test1) includes my subnet IP "10.10.72.146/32" but I also specifically added it (test2). Based on this, I'm supposed to be getting JUST the adc load balancer (10.233.46.163). Any idea what I could be doing wrong?
Thanks for any suggestion!!
The text was updated successfully, but these errors were encountered: