search

nginxinc / kubernetes-ingress

NGINX and NGINX Plus Ingress Controllers for Kubernetes
https://docs.nginx.com/nginx-ingress-controller
Apache License 2.0
4.68k stars 1.97k forks source link

VirtualServers stays INVALID after NIC POD (re)start #5358

Open hafe opened 7 months ago

hafe commented 7 months ago

Describe the bug

VirtualServers stays INVALID after NIC POD (re)start

Loading the configuration to a running NIC works. After restart of the POD the VirtualServers stays INVALID forever. NGINX however has a valid configuration and handles traffic. When the reload timeout is increased from default 60s the VirtualServers become VALID.

To Reproduce See above

Expected behavior VirtualServers should be VALID despite how many of them

Your environment

Reproduced in the following env:

Additional context This line in ./kubernetes-ingress/internal/nginx/verify.go logs: return fmt.Errorf("could not get expected version: %v after %v", expectedVersion, c.timeout)

github-actions[bot] commented 7 months ago

Hi @hafe thanks for reporting!

Be sure to check out the docs and the Contributing Guidelines while you wait for a human to take a look at this :slightly_smiling_face:

Cheers!

hafe commented 7 months ago

Compiling the policies is what seems to take time. Notable is it works when the resources are added to a running NIC but not as soon as it start/restarts.

hafe commented 7 months ago

All VS goes invalid the same moment the leader election gets ready.

shaun-nx commented 5 months ago

Linking related slack thread here too just to keep things together.