Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
spring-cloud-kubernetes-fabric8-leader v2.1.3 does not refresh k8s auth tokens
See original GitHub issueDescribe the bug
When using spring-cloud-kubernetes-fabric8-leader v2.1.3, the auth tokens against k8s aren’t refreshed automatically.
Fabric8 Kubernetes Client version
5.10.2 (according to the spring-cloud-kubernetes-fabric8-autoconfig v2.1.3 POM)
Steps to reproduce
We are getting warnings in our GCP audit logs from our usage of spring leader election:
[authentication.k8s.io/stale-token](http://authentication.k8s.io/stale-token):
"subject: system:serviceaccount:default:my-app-api, seconds after warning threshold: 798"
spring-cloud-kubernetes-fabric8-leader should have their k8s libraries updated to be able to refresh the auth token. The kubernetes java library version 14.0.0 or later should be OK since it includes a token refresh fix.
Expected behavior
The k8s auth tokens should be refreshed regularly.
Runtime
Kubernetes (vanilla)
Kubernetes API Server version
1.22
Environment
GKE
Fabric8 Kubernetes Client Logs
No response
Additional context
No response
Issue Analytics
- State:
- Created a year ago
- Comments:8 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
We’re not involved with that project, but I hope so.
I recall @wind57 was interested on upgrading https://github.com/spring-cloud/spring-cloud-kubernetes/issues/1048, maybe he can provide more details.
Maybe not for all cluster flavors, but for most of them yes.
It’ll be part of 6.1.0 which I’m currently preparing to release.