NGINX Ingress Controller Causes Hosts to Return 404 and 'Connection Not Private' After Restart

General Discussions
1

After restarting the nginx-ingress-controller deployment, the hosts display the error message: “Your connection is not private.” Upon inspecting the logs, I observe that a 404 status code is returned. However, once I edit the associated Ingress resource by adding any test label, the hosts become accessible again, and the logs show a 200 status code, indicating successful connections.

This behavior seems to be inconsistent and unexpected, as the hosts should be accessible immediately after the controller restart without needing any manual intervention.

NGINX Ingress controller
Release: v1.11.4
Build: ba0f2ee
Repository: GitHub - kubernetes/ingress-nginx: Ingress NGINX Controller for Kubernetes
nginx version: nginx/1.25.5

kubectl version
Client Version: v1.31.1
Kustomize Version: v5.4.2
Server Version: v1.31.4-gke.1372000

Node Version: v1.30.9-gke.1046000

Do let me know if any more information is required.
Appreciate help here.

2

Issue resolved as below block was missing from rbac resources (clusterrole and role)

- apiGroups:
      - "networking.k8s.io"
    resources:
      - ingresses
      - ingressclasses
    verbs:
      - get
      - list
      - watch