Nginx pods running for Internal Ingress but unable to get the NGINX default website

[nidiculageorge]

The pods are running ,but when i browse the IP of the NGINX the service IP ,we are not getting the NGINX default page.As a result site hosted behind this NGINX is not accessible

What you expected to happen:

The NGINX default pasge should be accessible right when we browse the Internal nginx service IP ,we tried accessing the page from a VM inside the same vnet

Not sure seems some configuration issue with the command

NGINX Ingress controller version (exec into the pod and run nginx-ingress-controller --version.):

Version : 1.10.5

Azure AKS

• How was the ingress-nginx-controller installed:

  • If helm was used then please show output of helm -n <ingresscontrollernamespace> get values <helmreleasename>
    PS C:\Users\nidicula\OneDrive - RM PLC\PlatformandEngineering\Work\AKS\KubecostSetup> helm -n nginx-internal get values ingress-nginx-internal
    USER-SUPPLIED VALUES:
    controller:
    admissionWebhooks:
    patch:
    nodeSelector:
    kubernetes.io/os: linux
    ingressClass: nginx-internal
    ingressClassResource:
    controllerValue: k8s.io/nginx-internal
    name: nginx-internal
    nodeSelector:
    kubernetes.io/os: linux
    replicaCount: 2
    service:
    annotations:
    service.beta.kubernetes.io/azure-load-balancer-health-probe-request-path: /readyz
    service.beta.kubernetes.io/azure-load-balancer-internal: true
    service.beta.kubernetes.io/azure-load-balancer-internal-subnet: net-asr-aks-ilb
    internal:
    enabled: true
    defaultBackend:
    nodeSelector:
    kubernetes.io/os: linux

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

The other external ingress controller is working fine

[k8s-ci-robot]

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-sigs/prow repository.

[nidiculageorge]

helm install ingress-nginx-internal ingress-nginx/ingress-nginx --namespace nginx-internal --set controller.replicaCount=2 --set controller.nodeSelector."kubernetes.io/os"=linux --set defaultBackend.nodeSelector."kubernetes.io/os"=linux --set controller.admissionWebhooks.patch.nodeSelector."kubernetes.io/os"=linux --set controller.service.internal.enabled=true --set controller.service.annotations."service.beta.kubernetes.io/azure-load-balancer-internal"="true" --set controller.service.annotations."service.beta.kubernetes.io/azure-load-balancer-internal-subnet"="
net-asr-aks-ilb" --set controller.service.annotations."service.beta.kubernetes.io/azure-load-balancer-health-probe-request-path"=/readyz --set controller.ingressClassResource.controllerValue="k8s.io/nginx-internal" --set controller.ingressClassResource.name=nginx-internal --set controller.ingressClass=nginx-internal --version 4.10.5

Used the above command to setup

[longwuyuan]

This is not a problem of the ingress-nginx controller.

[longwuyuan]

/remove-kind bug

If you answer the questions asked in a new bug report template, and write a procesdure to reproduce the problem in a kind cluster, the readers here can try to reproduce the problem or analyze the data you have posted.

[nidiculageorge]

@longwuyuan where whould i raise the above issue

[longwuyuan]

You have not provided the answers to the questions that are asked in the template of a new bug report so there is no data to analyze and make any comments. Your website could be done for several reasons and the none of ht einformation posted here shows it is caused by the ingress-nginx controller.

[nidiculageorge]

@longwuyuan we have used the below command

helm install ingress-nginx-internal ingress-nginx/ingress-nginx --namespace nginx-internal --set controller.replicaCount=2 --set controller.nodeSelector."kubernetes.io/os"=linux --set defaultBackend.nodeSelector."kubernetes.io/os"=linux --set controller.admissionWebhooks.patch.nodeSelector."kubernetes.io/os"=linux --set controller.service.internal.enabled=true --set controller.service.annotations."service.beta.kubernetes.io/azure-load-balancer-internal"="true" --set controller.service.annotations."service.beta.kubernetes.io/azure-load-balancer-internal-subnet"="
net-asr-aks-ilb" --set controller.service.annotations."service.beta.kubernetes.io/azure-load-balancer-health-probe-request-path"=/readyz --set controller.ingressClassResource.controllerValue="k8s.io/nginx-internal" --set controller.ingressClassResource.name=nginx-internal --set controller.ingressClass=nginx-internal --set controller.admissionWebhooks.patch.image.digest="" --set controller.extraArgs.enable-ssl-passthrough="" --set controller.service.public="false" --version 4.10.5

We got an internal IP with load balancer as below

As per the access we should be able to access the IP to get the nginx page .

But when we browse the Internal IP we are not able to get the pasge. Is there something MISSING IN the command .Also we tried browsing the pod IP .It works .But LB IP which should be the IP of the NGINX is not working

[longwuyuan]

Consider these facts ;

• The new bug report template asked you questions but you ignored them
• I asked you to help by answering questions in the new bug report but you ignored that request
• As a result there is no info here for any readers to analyze and base any helpful comments on
• Your expectations is fair that you will just type some random info like in a chat and get enough help to resolve the problem. But most github issue engagements requires you to provide information that can be used to reproduce an issue and/or analyzed.
• Every user of this controller can get a HTTP response with a vanilla non-complex ingress so there is nothing to test about the controller, that relates to your problem. Hence the problem is specific to your environment and config

So either help the readers here and answer the questions asked in a new bug report template because there is hardly any resource to provide support here like you expect. Or talk in the kubernetes.slack.com in the ingress-nginx-users channel as there are many many more people there .

Also, screenshots dont facilitate analysis. Copy/pasting the commands you used to debug the problem (and the output of those commands) potentially becomes data that readers can analyze and base comments on