You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Kernel (e.g. uname -a):
Linux nginx-ingress-controller-758fd9d646-t82vl 4.13.0-1018-azure 413 Request Entity Too Large #21-Ubuntu SMP Thu May 17 13:58:38 UTC 2018 x86_64 GNU/Linux
Install tools:
Others:
What happened:
I have a Kubernetes cluster on Azure ACS and deployed ingress-nginx with the following yaml files. The root path works and successfully routes me to serviceone but any other route does not work.
Making a request to 'External-IP/servicetwo' returns a 404 from the browser not from the default-backend 404.
I run all of the following with kubectl apply -f filename.yml
kind: Deployment
metadata:
name: servicetwo
namespace: ingress-nginx
spec:
replicas: 1
template:
metadata:
labels:
app: servicetwo
spec:
containers:
- name: servicetwo
image: wregistry.azurecr.io/linux_xorigin:v1
imagePullPolicy: IfNotPresent
ports:
- containerPort: 80
name: servicetwo
imagePullSecrets:
- name: regcred
---
apiVersion: v1
kind: Service
metadata:
name: servicetwo
namespace: ingress-nginx
spec:
type: NodePort
ports:
- port: 80
selector:
app: servicetwo
---
apiVersion: apps/v1beta1
kind: Deployment
metadata:
name: serviceone
namespace: ingress-nginx
spec:
replicas: 1
template:
metadata:
labels:
app: serviceone
spec:
containers:
- name: serviceone
image: wregistry.azurecr.io/api_xorigin:v1
imagePullPolicy: IfNotPresent
ports:
- containerPort: 80
name: serviceone
imagePullSecrets:
- name: regcred
---
apiVersion: v1
kind: Service
metadata:
name: serviceone
namespace: ingress-nginx
spec:
type: NodePort
ports:
- port: 80
selector:
app: serviceone
---
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
name: my-ingress
annotations:
kubernetes.io/ingress.class: "nginx"
kubernetes.io/ingress.allow-http: "true"
nginx.ingress.kubernetes.io/ssl-redirect: "false"
ingress.kubernetes.io/rewrite-target: /
nginx.ingress.kubernetes.io/enable-cors: "true"
nginx.ingress.kubernetes.io/cors-allow-methods: "PUT, GET, POST, OPTIONS"
namespace: ingress-nginx
spec:
rules:
- http:
paths:
- path: /
backend:
serviceName: serviceone
servicePort: 80
- path: /servicetwo
backend:
serviceName: servicetwo
**Is this a BUG REPORT or FEATURE REQUEST?** (choose one):
BUG REPORT
I've looked into all other similar reports and tried all of the solutions but none works for me.
<!--
If this is a BUG REPORT, please:
- Fill in as much of the template below as you can. If you leave out
information, we can't help you as well.
If this is a FEATURE REQUEST, please:
- Describe *in detail* the feature/behavior/change you'd like to see.
In both cases, be ready for followup questions, and please respond in a timely
manner. If we can't reproduce a bug or think a feature already exists, we
might close your issue. If we're wrong, PLEASE feel free to reopen it and
explain why.
-->
**NGINX Ingress controller version**:
quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.16.2
**Kubernetes version** (use `kubectl version`):
Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.2", GitCommit:"5fa2db2bd46ac79e5e00a4e6ed24191080aa463b", GitTreeState:"clean", BuildDate:"2018-01-18T10:09:24Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"windows/amd64"}
Server Version: version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.13", GitCommit:"290fb182489a396dce5d136451388f9b12f29c94", GitTreeState:"clean", BuildDate:"2018-05-15T18:08:47Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}
**Environment**:
- **Cloud provider or hardware configuration**:
Azure ACS
- **OS** (e.g. from /etc/os-release):
PRETTY_NAME="Debian GNU/Linux 9 (stretch)"
NAME="Debian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
- **Kernel** (e.g. `uname -a`):
Linux nginx-ingress-controller-758fd9d646-t82vl 4.13.0-1018-azure #21-Ubuntu SMP Thu May 17 13:58:38 UTC 2018 x86_64 GNU/Linux
- **Install tools**:
- **Others**:
**What happened**:
I have a Kubernetes cluster on Azure ACS and deployed ingress-nginx with the following yaml files. The root path works and successfully routes me to serviceone but any other route does not work.
Making a request to 'External-IP/servicetwo' returns a 404 from the browser not from the default-backend 404.
I run all of the following with kubectl apply -f filename.yml
https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/mandatory.yaml
```apiVersion: apps/v1beta1
kind: Deployment
metadata:
name: servicetwo
namespace: ingress-nginx
spec:
replicas: 1
template:
metadata:
labels:
app: servicetwo
spec:
containers:
- name: servicetwo
image: wregistry.azurecr.io/linux_xorigin:v1
imagePullPolicy: IfNotPresent
ports:
- containerPort: 80
name: servicetwo
imagePullSecrets:
- name: regcred
---
apiVersion: v1
kind: Service
metadata:
name: servicetwo
namespace: ingress-nginx
spec:
type: NodePort
ports:
- port: 80
selector:
app: servicetwo
---
apiVersion: apps/v1beta1
kind: Deployment
metadata:
name: serviceone
namespace: ingress-nginx
spec:
replicas: 1
template:
metadata:
labels:
app: serviceone
spec:
containers:
- name: serviceone
image: wregistry.azurecr.io/api_xorigin:v1
imagePullPolicy: IfNotPresent
ports:
- containerPort: 80
servicePort: 80
I've also tried adding the wildcards on the routes. This causes no paths two work and returns a 404 from the default-backend from for External-IP/ and External-IP/servicetwo.
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
BUG REPORT
I've looked into all other similar reports and tried all of the solutions but none works for me.
NGINX Ingress controller version:
quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.16.2
Kubernetes version (use
kubectl version
):Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.2", GitCommit:"5fa2db2bd46ac79e5e00a4e6ed24191080aa463b", GitTreeState:"clean", BuildDate:"2018-01-18T10:09:24Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"windows/amd64"}
Server Version: version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.13", GitCommit:"290fb182489a396dce5d136451388f9b12f29c94", GitTreeState:"clean", BuildDate:"2018-05-15T18:08:47Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}
Environment:
Cloud provider or hardware configuration:
Azure ACS
OS (e.g. from /etc/os-release):
PRETTY_NAME="Debian GNU/Linux 9 (stretch)"
NAME="Debian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
Kernel (e.g.
uname -a
):Linux nginx-ingress-controller-758fd9d646-t82vl 4.13.0-1018-azure 413 Request Entity Too Large #21-Ubuntu SMP Thu May 17 13:58:38 UTC 2018 x86_64 GNU/Linux
Install tools:
Others:
What happened:
I have a Kubernetes cluster on Azure ACS and deployed ingress-nginx with the following yaml files. The root path works and successfully routes me to serviceone but any other route does not work.
Making a request to 'External-IP/servicetwo' returns a 404 from the browser not from the default-backend 404.
I run all of the following with kubectl apply -f filename.yml
https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/mandatory.yaml
I've also tried adding the wildcards on the routes. This causes no paths two work and returns a 404 from the default-backend from for
External-IP/
andExternal-IP/servicetwo
.What you expected to happen:
I expected ingress to be able to route the requests to the correct services.
How to reproduce it (as minimally and precisely as possible):
Run an Azure ACS kubernetes cluster. Deploy and expose two services then run these yaml files:
https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/mandatory.yaml
https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/provider/cloud-generic.yaml
next run the following with the correct service names substituted in
Anything else we need to know:
there following is the
nginx.conf
from/etc/nginx/nginx.conf
from the pod running my nginx controllerThe text was updated successfully, but these errors were encountered: