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(73.60000000000001, 71%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EVP%3C/text%3E%3C/svg%3E)
While accessing the url i am getting 404 not found error please help me on this.
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: athena-microservices-to-mckup-ingress
namespace: support-personalization-np
annotations:
kubernetes.io/ingress.allow-http: 'false'
kubernetes.io/ingress.class: nginx
ncp/http-redirect: 'true'
ncp/use-regex: 'true'
nginx.ingress.kubernetes.io/proxy-body-size: '0'
spec:
rules:
- host: athena-microservices-to-mckup.prdlvgpu1.aiaccel.dell.com
http:
paths:
- path: /graphql
pathType: Prefix
backend:
service:
name: athena-microservices-to-mckup-service
port:
number: 5001
tls:
- hosts:
- athena-microservices-to-mckup.prdlvgpu1.aiaccel.dell.com
Hello Vinayak Patil
Welcome to Microsoft Q&A Platform, thanks for posting your query here.
Based on the details provided, looks like you have created an Ingress resource to expose your service over HTTPS. However, you are getting a 404 not found error while accessing the URL.
Just check the logs of the Ingress controller to see if there are any errors.
Ref: https://techcommunity.microsoft.com/t5/fasttrack-for-azure/kubernetes-nginx-ingress-controller-logs/ba-p/3684217
Please try these troubleshooting steps and see if these help:
-Make sure that your service is running and accessible within the cluster. You can check this by running the following command:
kubectl get svc -n support-personalization-np
This will list all the services in the support-personalization-np namespace. Make sure that the athena-microservices-to-mckup-service service is running and has a valid IP address.
-Check if the Ingress resource is created successfully by running the following command:
kubectl get ingress -n support-personalization-np
-Check if the DNS record for athena-microservices-to-mckup.prdlvgpu1.aiaccel.dell.com is pointing to the IP address of the Application Gateway. You can check this by running the following command:
nslookup athena-microservices-to-mckup.prdlvgpu1.aiaccel.dell.com
-Check if the path /graphql is correct and accessible. You can test this by running the following command:
curl -k https://athena-microservices-to-mckup.prdlvgpu1.aiaccel.dell.com/graphql
Hope this helps.
Hello Vinayak Patil
If the DNS settings are correct and the IP address is correct, then the issue might be with the backend service or the Ingress configuration.
To further troubleshoot this,
-Check whether the backend service is running and accessible. You can use the kubectl get svc command to list all the services in your cluster and check whether the athena-microservices-to-mckup-service service is running and has a valid IP address. If the service is not running or has an incorrect IP address, you need to fix the service configuration.
-Check whether the backend service is accessible from within the cluster. You can use the kubectl exec command to access a shell inside a pod and try to access the backend service using curl or wget. If you are able to access the backend service from within the cluster, then the issue might be with the Ingress configuration.
-Check the logs of the Ingress controller pod. You can use the kubectl logs command to get the logs of the Ingress controller pod and see whether there are any errors or warnings related to the Ingress configuration.
If none of these troubleshooting steps help resolved your issue, I would recommend you to open a azure support case. Support team will be able to check and help on this.