Ingress correctly map the path but resolve incorrect Pod IP Address

[yukihonhk]

NGINX Ingress controller version: 0.30

Kubernetes version (use kubectl version): AKS 1.21

Environment: PROD

• Cloud provider or hardware configuration: Azure

• OS (e.g. from /etc/os-release): Ubuntu 18.04.5

• Kernel (e.g. uname -a): No resolver when using external auth #51~18.04.1-Ubuntu

• Install tools:

  • Please mention how/where was clsuter created like kubeadm/kops/minikube/kind etc.

• Basic cluster related info:

  • kubectl version 1.21
  • kubectl get nodes -o wide
    NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME
    aks-nodepool1-46409549-vmss000000 Ready agent 45d v1.21.1 10.155.130.4 Ubuntu 18.04.5 LTS 5.4.0-1049-azure containerd://1.4.4+azure
    aks-nodepool1-46409549-vmss000001 Ready agent 45d v1.21.1 10.155.130.115 Ubuntu 18.04.5 LTS 5.4.0-1049-azure containerd://1.4.4+azure
    aks-userpool1-46409549-vmss000000 Ready agent 45d v1.21.1 10.155.130.226 Ubuntu 18.04.5 LTS 5.4.0-1049-azure containerd://1.4.4+azure

• How was the ingress-nginx-controller installed:

  • If helm was used then please show output of helm ls -A

  • NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
    internal-ingress ingress-basic 1 2021-08-23 15:45:01.3973482 +0800 CST deployed ingress-nginx-3.36.0 0.30.0

  • If helm was used then please show output of helm -n <ingresscontrollernamepspace> get values <helmreleasename>
    USER-SUPPLIED VALUES:
    controller:
    admissionWebhooks:
    patch:
    nodeSelector:
    beta.kubernetes.io/os: linux
    nodeSelector:
    beta.kubernetes.io/os: linux
    replicaCount: 2
    service:
    annotations:
    service.beta.kubernetes.io/azure-load-balancer-internal: "true"
    loadBalancerIP: 10.155.131.254
    defaultBackend:
    nodeSelector:
    beta.kubernetes.io/os: linux
    PS C:\windows\system32>

  • If helm was not used, then please explain how the ingress-nginx-controller was installed or copy/paste the command used to install the controller below

  • if you have more than one instance of the ingress-nginx-controller installed in the same cluster, please provide details for all the instances

• Current State of the controller:

  • kubectl -n <ingresscontrollernamespace> get all -A -o wide
  • kubectl -n <ingresscontrollernamespace> describe po <ingresscontrollerpodname>
  • kubectl -n <ingresscontrollernamespace> describe svc <ingresscontrollerservicename>

• Current state of ingress object, if applicable:

  • kubectl -n <appnnamespace> get all,ing -o wide
  • kubectl -n <appnamespace> describe ing <ingressname>
  • If applicable, then, your complete and exact curl/grpcurl command (redacted if required) and the reponse to the curl/grpcurl command with the -v flag

• Others:

  • Any other related information like ;
    • copy/paste of the snippet (if applicable)
    • kubectl describe ... of any custom configmap(s) created and in use
    • Any other related information that may help

What happened:

What you expected to happen:
504 gateway timeout and the Ingress correctly map the path but resolve incorrect Pod IP Address

Ingress correctly map the path but resolve incorrect Pod IP Address
How to reproduce it:
cannot reproduce

Anything else we need to know:

/kind bug

[k8s-ci-robot]

@yukihonhk: This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

[longwuyuan]

/remove-kind bug
/kind support
@yukihonhk please provide the information requested in the template in case you still need someone to analyse the config a and logs related to the problem. ALso suggest please install the latest release of the Ingress-NGINX controller as there are many changes and bug fixes you are missing

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[kundan2707]

/remove-lifecycle stale

[kundan2707]

@yukihonhk friendly ping
please provide detail information to work on

[kundan2707]

/assign

[kundan2707]

@yukihonhk if issue does not exits further and everything is fiine then you can close issue

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue.

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

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.