intermittent errors from client informer

[LinMoskovitch]

Hi, We are facing sporadic "Unauthorized" issues in k8s go-client creation:

pkg/mod/k8s.io/client-go@v0.28.5/tools/cache/reflector.go:229: Failed to watch <resource_kind>: the server has asked for the client to provide credentials (get <resource_kind>)

log: pkg/mod/k8s.io/client-go@v0.28.5/tools/cache/reflector.go:229: Failed to watch <resource_kind>: failed to list *<resource_kind>: Unauthorized

• expirationSeconds is configured to 10m, and the credentials rotation is configured to 80% of the expiration time (=480sec).

We tried to replicate the issue in actual code flow using the following steps but had no luck:

• We created multiple clients on the same secret and requested various resources.
• We attempted to reduce the expirationSeconds to less than 10m.

Has anyone else encountered this kind of issue? If so, do you have any suggestions on how to resolve or investigate it?

Thanks.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale