laurens-gross-mw commented on issue #543: URL: https://github.com/apache/pekko-management/issues/543#issuecomment-3615764397
> > Hi [@pjfanning](https://github.com/pjfanning), > > Thank you for the tip about the config value. This was very helpful to solve the version conflict. > > We tested the snapshot version on our system yesterday and the result was successful. The same pod was able to request a new lease from the k8s API - before and after the token rotation. So, from our point of view, the fix works perfectly - many thanks for all your help. > > Glad to hear that it works! Out of curiosity, did you observe the warning log about the old token not being valid or was the rotation entirely clean (i.e. the token being rotated out has enough of a buffer so it doesn't return Unauthorized) Yes, I checked the logs this morning and I can find the log for retry. In the screenshot, you can see, that this log is logged multiple times, but the lease was acquired. Is the log correct, because it could be, that the request was answered with another status code? <img width="1072" height="1156" alt="Image" src="https://github.com/user-attachments/assets/9ab94db0-0d1b-4a04-8efb-3bf30634bee2"; /> The first token was issued at 13:32:52 and was valid until 14:32:52, the second token was issued at 14:21:13 and was valid until 15:21:13. So, from the token validity no retry was needed. Getting the lease work both times, but the logs suggest there were issues with the call to the k8s api -- 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]
