# Leadership

**URL:** <https://discuss.kubernetes.io/t/leadership/23334>\
**Category:** General Discussions\
**Created:** [March 6, 2023, 10:08pm UTC](https://discuss.kubernetes.io/t/leadership/23334 "2023-03-06T22:08:13Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![nappertr](https://avatars.discourse-cdn.com/v4/letter/n/7ab992/32.png) [@nappertr](https://discuss.kubernetes.io/u/nappertr)\
**Post date:** [March 6, 2023, 10:08pm UTC](https://discuss.kubernetes.io/t/leadership/23334/1 "2023-03-06T22:08:13Z")

</div>

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?

Thanks