mdedetrich commented on PR #546: URL: https://github.com/apache/pekko-management/pull/546#issuecomment-3556338140
> Hi @mdedetrich, regarding: > > > implies there may be some bottleneck/performance considerations in how often this API method is called. > > I mean if the API is called every now and then, even it being blocking wouldn't be a real issue in production??? If there is a performance consideration then I probably should implement a cache (but in doing so I need to know how long it is before an old token that is rotated out expires). @raboof @laurens-gross-mw maybe you have some context here? > > A token is 1h valid and has ~5min overlap with a new token in our system. So from our side, no caching is needed Is this setup where tokens have an overlap standard across all k8s deployments? Can it be configured to not have an overlap (if so it sounds like by default we should not be doing a retry on 401 but a user can configure this if they need to). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
