Handling Forbidden (403) HTTP Status Related Shutdowns is Informers

[csviri]

Is your enhancement related to a problem? Please describe

In Java Operator SDK there is a related issue where we would like to handle the situation when an RBAC permission is either not present or in the more pressing case (related to this issue) is removed while the informer is running.
operator-framework/java-operator-sdk#1422

In the first iteration we would like to periodically try to reconnect the watch. Currently (v6.0.0) in case of HTTP 403 the informer gracefully shuts down. There is no callback or other way to get notified about the shutdown.

Describe the solution you'd like

I see two possible approach now. Have a callback method to notify the users when an informer stops. So with a logic in JOSDK it can be restarted,

or

Have a more configurable retry options (with a possibility to indefinitely retry) for this use case.

Describe alternatives you've considered

No response

Additional context

No response