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
Path based routing only works with base path #2132
Comments
I run into the same issue just by following the AKS tutorial: https://docs.microsoft.com/en-us/azure/aks/ingress |
Closing. The issue with the article is the prefix of the annotations, it should be |
@evillgenius75 please reopen if you have more questions |
We are still seeing this even with the new annotation. /reopen |
@Kargakis: you can't re-open an issue/PR unless you authored it or you are assigned to it. 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/test-infra repository. |
Versions: kubernetes v1.9.7 |
/kind bug |
I am also encountering this with: quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.16.2 @aledbf , essentially all ingress paths except for root get ignored as long as I am attempting to use https. Is this a known issue? I'm trying to use nginx ingress with ssl-passthrough so that my backend Tomcat-based containers can perform TLS termination. Our application requires dual authentication so that x509 user certificate details can be passed along (DOD requirement). Do you have any thoughts as to why only the root ingress path is being used and all others ignored? Any help is appreciated. Ingress:
Controller deployment:
|
Please remove |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@fejta-bot: 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/test-infra repository. |
Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see https://kubernetes.io/docs/tasks/debug-application-cluster/troubleshooting/.):
What keywords did you search in NGINX Ingress controller issues before filing this one? (If you have found any duplicates, you should instead reply there.):
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
Bug Report
NGINX Ingress controller version:
10.2 and 11.0
Kubernetes version (use
kubectl version
):1.9.3 and 1.8.2
Environment:
Azure AKS and Azure ACS-Engine Cluster
uname -a
): 4.11.0-1015-azurekube-lego for TLS management
What happened:
Ingress rule to do TLS secure path based routing only routes correctly to default path "/" and not the second service on path "/hello2"
What you expected to happen:
If I go to http://url/ the service that is expected is return, however if I go to http://url/hello2 I get a generic 404 Not Found
How to reproduce it (as minimally and precisely as possible):
helm install stable/nginx-ingress
orhelm install stable/nginx --set controller.image.tag=0.11.0
kubectl get svc -w
3a. If using Azure provided DNS use this script:
3b. Get FQDN of PublicIP
az network public-ip list --query "[?contains(ipAddress, '52.224.125.195')].[dnsSettings.fqdn]" --output tsv
Install kube-lego and modify LEGO_EMAIL to a real email address
helm install stable/kube-lego \
--set config.LEGO_EMAIL=user@contoso.com \
--set config.LEGO_URL=https://acme-v01.api.letsencrypt.org/directory
Create 2 services to host behind proxy
helm repo add azure-samples https://azure-samples.github.io/helm-charts/
helm install azure-samples/aks-helloworld
helm install azure-samples/aks-helloworld --set title="AKS Ingress Demo" --set serviceName="ingress-demo"
Create an ingress yaml. Be sure to change host entry to the FQDn retrieved in step 3b or one you created in your own DNS provider:
Anything else we need to know:
Both web services are working correctly. If I switch the name of the services you can see the different backends but only when using base path "/"
TLS is working correctly and site is signed as expected.
nginx.conf file:
The text was updated successfully, but these errors were encountered: