Callback k8s client hangs when a reflector cannot be initialized

[fabriziosestito]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

The first time a request using a reflector is received, we initialize the reflector for the given resource/selectors.
If the fetching of the initial resource list fails, the reflector does not return as ready, therefore the client hangs indefinitely. As a result, the policy waits till the Kubernetes API server timeout is reached.

Expected Behavior

If the reflector initialization fails, the client should return an error.

[flavio]

Reopening, we reverted the fix because it was causing performance issues on the 1st query of context aware resources.

We need to find a way to notify the policy that the data we're feeding into wasm is stale.