Site Unreachable via Ingress Resource on Kubernetes

Overview

This incident type occurs when a website or service deployed on Kubernetes is not accessible via the ingress resource. The incident may be caused by various issues such as the ingress controller not running, misconfigured ingress resources, incorrect service selectors, and no running pods associated with the service. Troubleshooting steps may involve checking the logs of the ingress controller, inspecting the created ingress resources, describing the service and pods, and making sure the ports and endpoints are properly configured.

Parameters

Debug

Check the connectivity to website

Check if ingress controller is running

Check the logs of ingress controller

Check the created ingress resources

Describe the ingress resources and verify the ingress resource configuration

Describe the service

Check if there are running pods associated with the service

Make sure the ports are matching to what you expected

Check the IP column to make sure it is going to the correct pod IP

Check the ingress configuration settings to ensure that they are properly set up and routing traffic to the correct destination.

Repair

Check the created ingress resources and verify that they are properly configured to route traffic to the intended service and port.