-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
GeoIP2 files present in /etc/ingress-controller/geoip, but the controller logs show "GeoLite2-City.mmdb not found" #11459
Comments
This issue is currently awaiting triage. If Ingress contributors determines this is a relevant issue, they will accept it by applying the The Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
I think I found the issue, the
Because obviously these files are not present anymore, because I only include the |
I have disabled |
/remove-kind bug Geoip legacy support was dropped in controlller v1.10 . So you could potentially use only geoip legacy in older versions of controller. I am not convinced you can have both enabled concurrently. /close |
@longwuyuan: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
What happened: I tried to download GeoIP2 databases from MaxMind manually, and attach them as a volume. The files (
GeoLite2-City.mmdb
andGeoLite2-ASN.mmdb
) are present in the machine under/etc/ingress-controller/geoip
, withwww-data:www-data
permissions. However, upon startup, I still see these logs:What you expected to happen: I expected the nginx controller to use the databases from the filesystem, because I want to avoid overhead of downloading from MaxMind on every new node launch in my Kubernetes cluster.
NGINX Ingress controller version:
v1.0.5
Kubernetes version:
v1.28.9-eks-036c24b
Environment:
uname -a
): Linux ingress-nginx-controller-4pvrl 5.10.217-205.860.amzn2.x86_64kubectl version
kubectl get nodes -o wide
How was the ingress-nginx-controller installed:
mandatory.yaml
.Current State of the controller:
kubectl describe ingressclasses
The above volume contains the files as mentioned already. The files are also accessible in the nginx ingress controller pods.
The text was updated successfully, but these errors were encountered: