Failure to start Nginx Ingress Controller on Kubernetes.

Overview

This incident type refers to the failure of starting Nginx Ingress Controller on Kubernetes. The incident may be caused by various factors such as resource constraints on the node, affinity rules, image pull issues, misconfigured RBAC, missing default server TLS Secret, missing or invalid annotations, and invalid values of ConfigMap keys. Troubleshooting these possible reasons involves checking the ingress-controller logs and events to identify the exact cause of the startup issue.

Parameters

Debug

List all nodes in the cluster

Check the status of the node where the ingress-controller is scheduled to run

View the resource requests and limits for the ingress-controller pod

Check the available resources on the node

Check the affinity rules for the ingress-controller deployment

Check the image pull status for the ingress-controller container

Check the ingress-controller logs for any errors during startup

Check the ingress-controller events for any errors during startup

Check the RBAC configuration for the ingress-controller service account

Check the annotations for the ingress resource

Check the values of the ConfigMap keys used by the ingress-controller

Repair

Check if there are resource constraints on the node where the Nginx Ingress Controller is deployed. Move the deployment to a node with more resources.