# Elastic-operator: deploying multiple data pods at once

**URL:** <https://discuss.elastic.co/t/elastic-operator-deploying-multiple-data-pods-at-once/381375>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Created:** [August 27, 2025, 2:07pm UTC](https://discuss.elastic.co/t/elastic-operator-deploying-multiple-data-pods-at-once/381375 "2025-08-27T14:07:33Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![idl0r](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/idl0r/32/144805_2.png) [@idl0r](https://discuss.elastic.co/u/idl0r)\
**Post date:** [August 27, 2025, 2:07pm UTC](https://discuss.elastic.co/t/elastic-operator-deploying-multiple-data-pods-at-once/381375/1 "2025-08-27T14:07:33Z")

</div>

Hi guys,

is it possible to let the elastic-operator deploy multiple data nods/pods at once?

We have 24 data nodes being evenly distributed on 3 kubernetes worker. We’d like to deploy multiple at once because otherwise it takes like 70 minutes currently.

Reducing the amount of data nodes isn’t possible, at least in the short term.

It’s not the PDB, so I assume it’s the operator itself that steers that?

---

<div class="post-metadata">

**Author:** ![michael.morello](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/michael.morello/32/47448_2.png) [@michael.morello](https://discuss.elastic.co/u/michael.morello)\
**Post date:** [August 27, 2025, 2:22pm UTC](https://discuss.elastic.co/t/elastic-operator-deploying-multiple-data-pods-at-once/381375/2 "2025-08-27T14:22:46Z")

</div>

Hello, I'm not sure to understand your question because only “master" nodes are added/removed one by one. Could you provide more details about what you want to achieve?

---

<div class="post-metadata">

**Author:** ![idl0r](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/idl0r/32/144805_2.png) [@idl0r](https://discuss.elastic.co/u/idl0r)\
**Post date:** [August 27, 2025, 2:29pm UTC](https://discuss.elastic.co/t/elastic-operator-deploying-multiple-data-pods-at-once/381375/3 "2025-08-27T14:29:31Z")

</div>

So when we do config changes / re-deploy or update the operator, it will recreate all pods and that one by one. We have 24 data pods/nodes and that’s taking quite some time.

We’d like to let it deploy multiple ones at once. Whoever controls that.

 ![pods](https://us1.discourse-cdn.com/elastic/original/3X/1/0/1074bc5fa190826c9cb4cb45521ba9f0b9241fb2.png)

You can see the age on the right side where you see that it starts with the last one first and goes up to data-0 which is still todo. So anything older ~1h is still to be deployed/recreated.

The 24 is from the ES SIEM nodeset

---

<div class="post-metadata">

**Author:** ![michael.morello](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/michael.morello/32/47448_2.png) [@michael.morello](https://discuss.elastic.co/u/michael.morello)\
**Post date:** [August 27, 2025, 2:47pm UTC](https://discuss.elastic.co/t/elastic-operator-deploying-multiple-data-pods-at-once/381375/4 "2025-08-27T14:47:12Z")

</div>

Did you try to increase `maxUnavailable` in the `changeBudget`: [Update strategy | Elastic Docs](https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s/update-strategy) ?

---

<div class="post-metadata">

**Author:** ![idl0r](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/idl0r/32/144805_2.png) [@idl0r](https://discuss.elastic.co/u/idl0r)\
**Post date:** [August 28, 2025, 8:32am UTC](https://discuss.elastic.co/t/elastic-operator-deploying-multiple-data-pods-at-once/381375/5 "2025-08-28T08:32:20Z")

</div>

That doesn’t seem to work. We have it set to 8 now but it’s still doing one by one. 😕

---

<div class="post-metadata">

**Author:** ![michael.morello](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/michael.morello/32/47448_2.png) [@michael.morello](https://discuss.elastic.co/u/michael.morello)\
**Post date:** [August 28, 2025, 8:44am UTC](https://discuss.elastic.co/t/elastic-operator-deploying-multiple-data-pods-at-once/381375/6 "2025-08-28T08:44:37Z")

</div>

Predicates that prevent Pods from being recreated are logged by the operator during the upgrade. This should help explain why only one Pod can be deleted at any given time.

---

<div class="post-metadata">

**Author:** ![idl0r](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/idl0r/32/144805_2.png) [@idl0r](https://discuss.elastic.co/u/idl0r)\
**Post date:** [August 28, 2025, 8:49am UTC](https://discuss.elastic.co/t/elastic-operator-deploying-multiple-data-pods-at-once/381375/7 "2025-08-28T08:49:59Z")

</div>

```auto
{"log.level":"info","@timestamp":"2025-08-28T08:45:56.225Z","log.logger":"elasticsearch-controller","message":"Cannot restart some nodes for upgrade at this time","service.version":"3.1.0+9fc9bb06","service.type":"eck","ecs.version":"1.4.0","iteration":"492","namespace":"siem","es_name":"siem","namespace":"siem","es_name":"siem","failed_predicates":{"if_yellow_only_restart_upgrading_nodes_with_unassigned_replicas":["siem-es-data-0","siem-es-data-1","siem-es-data-10","siem-es-data-2","siem-es-data-3","siem-es-data-4","siem-es-data-5","siem-es-data-6","siem-es-data-7","siem-es-data-8","siem-es-data-9","siem-es-masters-0"]}}

```

Any chance to relax / change that?