I have a question of leadership election: The leader election algorithm is clear and works fine, if a lock resource is required on a pod base, where the identity would be something like the ip address. What if the lock needs to be based on some additional entity, like car-model. This means that request for a specific model can only be processed by a specific pod. So, the idea is to have one lock resource per model (-lock) with the Identity -.
Is there a limit on how many lease objects could be handled by the kubernetes leaderelection api?