# Common userPlaceholder / podPriority configuration for multiple Z2JH instances

**URL:** <https://discourse.jupyter.org/t/common-userplaceholder-podpriority-configuration-for-multiple-z2jh-instances/30020>\
**Category:** Zero to JupyterHub on Kubernetes\
**Tags:** help-wanted\
**Created:** [November 12, 2024, 10:33am UTC](https://discourse.jupyter.org/t/common-userplaceholder-podpriority-configuration-for-multiple-z2jh-instances/30020 "2024-11-12T10:33:57Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![dev-dsp](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.jupyter.org/dev-dsp/32/15859_2.png) [@dev-dsp](https://discourse.jupyter.org/u/dev-dsp)\
**Post date:** [November 12, 2024, 10:33am UTC](https://discourse.jupyter.org/t/common-userplaceholder-podpriority-configuration-for-multiple-z2jh-instances/30020/1 "2024-11-12T10:33:57Z")

</div>

Hello!

In my setup, I have multiple Z2JH deployments running within a single Kubernetes cluster, each with user-placeholders configured. Currently, it appears that each placeholder is only preempted by the user-servers belonging to its respective parent Hub, which makes sense in terms of resource management. However, I am looking for a way to configure this so that when any user-server is created, it can utilize any available placeholder, regardless of which Hub it belongs to.

Is there a way to achieve this cross-Hub placeholder pooling?

Thank you in advance!

---

<div class="post-metadata">

**Author:** ![consideRatio](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.jupyter.org/consideratio/32/1033_2.png) [@consideRatio](https://discourse.jupyter.org/u/consideRatio)\
**Post date:** [November 12, 2024, 12:28pm UTC](https://discourse.jupyter.org/t/common-userplaceholder-podpriority-configuration-for-multiple-z2jh-instances/30020/2 "2024-11-12T12:28:05Z")

</div>

> Currently, it appears that each placeholder is only preempted by the user-servers belonging to its respective parent Hub

Oh, that would be unexpected. Are you having dedicated nodes for the various hubs in the cluster? Then this would happen, otherwise its unexpected to me.