Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Hi there,
There could be a few things you can check to ensure everything is set up correctly and to identify the root cause of the 404 error:
ingress-nginx LoadBalancer service. You can check the IP address of the LoadBalancer with the following command:kubectl get svc -n ingress-nginx
ingress-nginx controller is running without any issues:kubectl get pods -n ingress-nginx
kubectl describe ingress myservice
# Replace <ingress-nginx-controller-pod-name> with the actual name of the controller pod
kubectl logs -n ingress-nginx <ingress-nginx-controller-pod-name>
kubectl get deployments kubectl get services
# Replace <myservice-pod-name> with the actual name of the pod
kubectl logs <myservice-pod-name>
hub/myservice:latest image is accessible and contains the correct application code.If you still encounter the 404 error after checking the above, please provide the output of the commands and any relevant logs.
Best,
Bobby