Support enabling GeoIP2 geofiltering on the NGINX ingress controller #1
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "geoip"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Changes
NGINX_GEOIPiningress.shscript for enabling/disabling the aforementioned new featuregeoip-values.yamlto ingress deps for use if enabledexternalTrafficPolicytoLocalby default (only necessary for geoip lookup, but should be a sane default so we have access to real client IPs)Notes
configuration-snippetannotation, which requires setting the controller'sannotations-risk-leveltoCritical. This is technically risky, as it allows all sorts of annotations to be configured on an ingress, but for a single person/org tenant cluster, this risk should not be of a big concern. Reference: https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/annotations-risk/#annotations-scope-and-riskexternalTrafficPolicytoLocalfrom its previous default value ofCluster. Reference: http://archive.today/2026.03.03-042921/https://medium.com/@zghanem/understanding-the-impact-of-externaltrafficpolicy-on-kubernetes-services-4f4426cb1246.