You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My goal was to have a single, long-lived etcd client for a web service.
According to etcd issues it would be up to client SDKs to implement auth token renewal on long-lived connections. aetcd currently doesn't do a token refresh and I got to experience that the hard way.
To reproduce:
configure your etcd cluster with a short auth-ttl
create and connect a client with aetcd
await TTL (calls made before the TTL expires will extend the TTL!)
make another call with the same client and the same connection -> aetcd.exceptions.UnauthenticatedError: etcdserver: invalid auth token
My goal was to have a single, long-lived etcd client for a web service.
According to etcd issues it would be up to client SDKs to implement auth token renewal on long-lived connections. aetcd currently doesn't do a token refresh and I got to experience that the hard way.
To reproduce:
auth-ttl
aetcd.exceptions.UnauthenticatedError: etcdserver: invalid auth token
As a workaround just use short-lived client connections wherever possible, á la:
I currently don't know if watchers are affected.
The text was updated successfully, but these errors were encountered: