This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(156.8, 78%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECP%3C/text%3E%3C/svg%3E)
Hi, We have a web project based on .NET which is containerized and published on ACR and further deployed on AKS. While performing the .NET version upgrade, since docker image on linux now doesn't runs on privileged port 80, hence we are exposing 8080 and 8081 using a non root user. Runs locally fine on Docker desktop, but when pushed on AKS the pods keep on failing which seems due to some mismatch in the different ports we have configured on deployment yaml, service yaml and ingress yaml. See below samples for all
DockerFile
Deployment yaml
Service yaml
ingress yaml
All these different port are confusing me and somehow the mismatch in one of these is resulting in pod failure. Note AKS version we are using is latest i.e. 1.31.5.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(294.40000000000003, 47%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMR%3C/text%3E%3C/svg%3E)
I can see Container (Dockerfile) Exposes 8080 & 8081 and 8080 is fine, but why 8081? If you don't need it, you can remove it.
https://learn.microsoft.com/en-us/dotnet/core/compatibility/containers/8.0/aspnet-port You must explicitly tell .NET to listen on the correct ports.
If you would like to expose both 8080 and 8081 ports, you must ensure deployment and service yaml file also include both the ports.
https://kubernetes.io/docs/concepts/services-networking/service/
Please let me know for any queries after you make changes and deploy.
Hi @Mounika Reddy Anumandla i have updated the docker image and tried deploying the service again using above ingress and deployment yaml, however pod gets crashbackloop fail error.Can you please suggest if the ports there are correct in these yaml's
As per my understanding, I have seen the Docker file,it does not seem to be an issue with the port numbers. Can you provide with the logs:
kubectl logs <pod-name> -n development
kubectl describe pod <pod-name> -n development
kubectl get events -n development
Hi @Mounika Reddy Anumandla Logs says that missing uri string in program.cs, however when i run the same on local it works fine.
Local Container logs:
AKS pod logs:
Pod descibe logs:
Somewhere the deployment yaml , service yaml or either of the ingress yaml ports are creating an issue it seems.. Can you verify those as mentioned above and see