Peter Brachwitz

Similar problem https://github.com/elastic/cloud-on-k8s/issues/6027 there it is a PVC resize that leads to multiple updates with an unchanging spec.

We discussed potential solutions and @barkbay suggested two approaches: * disabling desired_nodes for the next release * switching to a conditional PUT after GET approach: 1. `GET` the `_lastest` desired...

Comparing the `_latest` desired nodes returned via the Elasticsearch API with the expected values turns out to be trickier than I thought: ``` {"service.version": "2.5.0-SNAPSHOT+dff6b534", "iteration": "1", "namespace": "default", "es_name":...

I am thinking about ways to optimise this. But it is quite involved. One idea follow below. First iteration: 1. `PUT` desired nodes topology and calculate the hash of the...

I have not been able to reproduce this issue. Are you sure there was not something else at play here? Also I wonder by what mechanism the deletion could possibly...

I think I misunderstood your initial bug report. I thought you were saying that the secret created and owned by the user (`system-cpu-config` in your example in the OP) had...

I think I am leaning toward your option 2. Option 1. is difficult because we have multiple conflicting cases here: * the secret in the API Server is different from...

I have reached out to the Elasticsearch team to figure out if we can improve something in the node shutdown API. What I need to understand better still is why...

So regarding the check for shard activity it looks like the cluster health API request timed out: ``` Jun 17, 2022 @ 07:18:09.543 task [cluster_health (wait_for_events [LANGUID])] timed out after...

I did a quick test, haven't looked at the code yet. But somehow the UI still does not show content  There is data flowing...