There is a pod called `pink-pod-cka16-trb` created in the `default` namespace in `cluster4`. This app runs on port `tcp/5000` and it is exposed to end-users using an ingress resource called `pink-ing-cka16-trb` in such a way that it is supposed to be accessible using the command: `curl http://kodekloud-pink.app` on `cluster4-controlplane` host.
However, this is not working. Troubleshoot and fix this issue, making any necessary to the objects.
`Note:` You should be able to ssh into the `cluster4-controlplane` using `ssh cluster4-controlplane` command.
=> I changed the protocol from udp to tcp and also scaled the coredns deploy to 2 replicas.(coredns is running also) But still **curl kodekloud-pink.app** is showing below error.
<html>
<head><title>404 Not Found</title></head>
<body>
<center><h1>404 Not Found</h1></center>
<hr><center>nginx</center>
</body>
</html>
How to mitigate this?
Also, you may need to check if the ingress resource was picked up by the ingress controller. The ingress-nginx IC, for example, will post something in its log when there’s a problem, like an issue with the ingressClassName you use.