Retry on status update failures #1016
Description
As a user of NKG
I want NKG to retry on status update failures
So that transient issues within Kubernetes do not prevent NKG from updating the status on its resources and leading me down a wrong debugging path when something goes wrong.
Acceptance
-When NKG fails to update status on a Kubernetes resource, it will retry if a relevant error is returned
- A small back off is implemented for each retry
- When the NKG pod context is cancelled, the status updater component will gracefully exit.
Original Issue:
It doesn't retry on failures. This means there is a chance that some resources will not have up-to-do statuses.
Statuses are important part of the Gateway API, so we need to ensure that the Gateway always keep the resources
statuses up-to-date.