Open SchiessMax opened 1 month ago
A short update from our side: The problem occured in our productive system, so we now removed the kubernetes lease from our code. We will use it again once it's more stable.
Thanks @SchiessMax for the update - we'll have to take a look at this too
Version Information Akka.Coordination.KubernetesApi 1.5.19 Akka.Cluster 1.5.19
Describe the bug We had a problem in our test system where a singleton could not be contacted over it's proxy any more. According to logs this might have happened because the lease was reaquired. The bug can be reproduced by simply deleting the kubernetes lease using kubectl. This leads to the service reacquiring the lease.
To Reproduce Steps to reproduce the behavior:
Expected behavior The lease is reacquired and the proxy can reach the singleton again
Actual behavior The lease was reacquired but the proxy could not reach the singleton.
Environment Are you running on Linux? Windows? Docker? Which version of .NET? net8.0, linux docker images inside a kubernetes cluster
Additional context Logs after start:
Logs after deleting the lease: