-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow passing SetWatchErrorHandler to created informers #2231
Comments
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
That makes sense. We should also likely provide a default implementation that uses the controller-runtime logger rather than klog, as the latter might not be enabled. |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /close not-planned |
@k8s-triage-robot: Closing this issue, marking it as "Not Planned". In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Currently, when a new informer is created, it will wait for a cache sync before returning to the caller.
Unless the provided context is canceled, this call blocks forever if the informer fails to perform the ListWatch operation, such as being given an invalid Kubernetes API server address or if the authentication is lacking appropriate credentials to access the requested resource.
I would like the ability to pass a WatchErrorHandler in cache.Options to created informers so I can log the specific error back to the user to help them understand why things aren't working.
Until this is available, there are two workarounds I've identified:
The text was updated successfully, but these errors were encountered: