Creating ingress causes 504/502 error

[rajeshkodali]

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):

NGINX Ingress controller version:
0.2.1

Kubernetes version (use kubectl version):
1.11.7

Environment:

• Cloud provider or hardware configuration:
  AWS
• OS (e.g. from /etc/os-release):
  Debian
• Kernel (e.g. uname -a):
  SMP Debian 4.9.110-3+deb9u2 (2018-08-13) x86_64 GNU/Linux
• Install tools:
• Others:

What happened:
Create new ingress rule, and new pods come up terminating old ones and cause 504 on cluster and 502 for a minute

What you expected to happen:

Dynamic reload without pod restarts or recreate

How to reproduce it (as minimally and precisely as possible):
Create and change ingress rules and apply

Anything else we need to know:

[aledbf]

Create new ingress rule, and new pods come up terminating old ones and cause 504 on cluster and 502 for a minute

Are you using probes in your application deployments?

[aledbf]

Also, please check https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/configmap/#proxy-next-upstream like proxy-next-upstream: error timeout http_502 http_504

[rajeshkodali]

Yes, I do use liveness and readiness checks on the application. Is it by design to create new pods on ingress changes?

[aledbf]

Is it by design to create new pods on ingress changes?

What do you mean?

[rajeshkodali]

I mean is ingress deployment suppose to create/re-create new pods on applying ingress changes? Isn't it suppose to be dynamically reload without bringing up new pods?

…

On Mon, Mar 18, 2019 at 9:13 AM Manuel Alejandro de Brito Fontes < ***@***.***> wrote: Is it by design to create new pods on ingress changes? What do you mean? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#3903 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ATHASbfZBgTA0qHSGiGjJZhWsCiVfRrDks5vX7sOgaJpZM4b5_6h> .

-- *Rajesh Kodali* *Sr. DevOps Engineer*

[aledbf]

I mean is ingress deployment suppose to create/re-create new pods on
applying ingress changes?

There is no pod/s creation when you create/change ingresses or any other scenario, the ingress controller only reaches the API server to sync the changes in the cluster.

What are you doing exactly?

[rajeshkodali]

It was just a create ingress. Below is the rule ``` apiVersion: extensions/v1beta1 kind: Ingress metadata: name: nginx-api-regex-rules annotations: nginx.ingress.kubernetes.io/use-regex: "true" nginx.ingress.kubernetes.io/rewrite-target: / nginx.ingress.kubernetes.io/ssl-redirect: "false" spec: rules: - http: paths: - path: /.*/api/ backend: serviceName: server servicePort: http ```

…

On Mon, Mar 18, 2019, 9:39 AM Manuel Alejandro de Brito Fontes < ***@***.***> wrote: I mean is ingress deployment suppose to create/re-create new pods on applying ingress changes? There is no pod/s creation when you create/change ingresses or any other scenario, the ingress controller only reaches the API server to sync the changes in the cluster. What are you doing exactly? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#3903 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ATHASaKOA5XkXkFplmgNUoUiG0AOa8gBks5vX8EygaJpZM4b5_6h> .

[aledbf]

@rajeshkodali first, please update to 0.23.0. After that please check https://kubernetes.github.io/ingress-nginx/examples/rewrite/#rewrite-target

[aledbf]

Your rule should look something like

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: nginx-api-regex-rules
  annotations:
    nginx.ingress.kubernetes.io/rewrite-target: /$1
    # without a TLS section, this does nothing
    # nginx.ingress.kubernetes.io/ssl-redirect: "false"
spec:
  rules:
  - host: ZZZZZZZZZZ
    http:
      paths:
      - backend:
          serviceName: server
          servicePort: http
        path: /.*/api/(.*)

[rajeshkodali]

I wish I can upgrade, I was having issues with 308 redirects on 0.22/0.23 . I couldn't try the fix mentioned in #2724 yet. I may have to live to 0.21 for a bit until it's tested