This message was deleted.

Anyone? Thanks.

the removal of worker nodes

I don't know, but this makes me think you're running in the cloud somewhere and not on baremetal? Some sort of scaler? There might be another way to block the removal depending on where you're running, but you'd need to include that info for context.

Yeah also relevant when autoscaling. But, this here is in the context of e.g. upgrading k3s on the cluster … where going by the cattle not pets approach and therefore NOT in-place upgrading but rather introducing new workers on the cluster ( on a newer k3s version ) and then removing old ones.

I still think the mechanism by which you're auto scaling and environment might be relevant, but then again...

We have both on-prem clusters and cloud

That's not really specific.

Hmm nope. Sorry not trying to sound annoyed here or anything like it. The initial question I ask - I think - is quite to the core … anything missing in regards to giving pointers on how to, in an automated fashion, control whether engine upgrades are ongoing?

Why even bother checking status? • Add a new node. • Mark it as a Longhorn node and wait for it to be ready. • Mark the node you're killing as disabled and set Eviction to True. • Wait until replicas = 0 • Delete the node.

Because I’ve experienced what making the mistake of removing workers also acting as longhorn nodes from the cluster … before engine upgrades had completed fully.

Is it possible to in an automated fashion, control whether X volume is going through an engine upgrade?

Is it setting what you are trying to achieve? https://longhorn.io/docs/1.6.1/deploy/upgrade/auto-upgrade-engine/#:~:text=This%20is%20a%20setting%20that%20controls%20how%20Longhorn%20automatically%20upgrades%20volumes%E2%80%99%20engines%20to%20the%20new%20default%20engine%20image%20after%20upgrading%20Longhorn%20manager.%20The%20value%20of%20this%20setting%20specifies%20the%20maximum%20number%20of%20engines%20per%20node%20that%20are%20allowed%20to%20upgrade%20to%20the%20default%20engine%20image%20at%20the%20same%20time.

Thank you @famous-journalist-11332 for chiming in. I already have that setting enabled. So I want to be able to know. E.g. in the case someone or something else upgrades longhorn and I run our introducing change code to e.g. upgrade k3s ( NOT in-place - removing old workers and introducing new ones ). From the outside - whether or not any engine upgrade is going on.