GeoIP2 docs mention incorrect folder for mounted volumes #11147
Labels
area/docs
kind/documentation
Categorizes issue or PR as related to documentation.
priority/important-longterm
Important over the long term, but may not be staffed and/or may need multiple releases to complete.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
What happened:
I tried to mount the geopip2 databases using a volume mount, using the paths in the official docs. After searching the github issues and the code I noticed the path used has changed:
from
/etc/nginx/geoip/
to/etc/ingress-controller/geoip/
specifically in this pr: #10470
This is not reflected in the docs:
https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/configmap/#use-geoip2
This line:
ingress-nginx/docs/user-guide/nginx-configuration/configmap.md
Line 734 in 3c4e78e
What you expected to happen:
GeoIP2 files to be mounted, and controller to start with GeoIP2 enabled.
NGINX Ingress controller version (exec into the pod and run nginx-ingress-controller --version.):
NGINX Ingress controller
Release: v1.10.0
Build: 71f78d4
Repository: https://github.com/kubernetes/ingress-nginx
nginx version: nginx/1.25.3
Kubernetes version (use
kubectl version
):Client Version: v1.29.2
Server Version: v1.28.5
Environment:
Cloud provider or hardware configuration: AKS
OS (e.g. from /etc/os-release): Ubuntu 22.04
Kernel (e.g.
uname -a
): 5.15.0-1057-azureInstall tools:
Basic cluster related info: Not Relevant, documentation issue
How was the ingress-nginx-controller installed: Helm
Current State of the controller: running
Current state of ingress object, if applicable: N/A
Others: N/A
How to reproduce this issue:
Anything else we need to know: No, setting the correct path works, so it's just a documentation issue
/kind documentation
/remove-kind bug
The text was updated successfully, but these errors were encountered: