Péter Láng

Now I can confirm that this issue happens on an actul production Kubernetes cluster with plenty of resources too. The operator erroneously decides to do a rolling restart and fails...

> @lpeter91 can you please test with the latest version of the operator? @prudhvigodithi Tried it, still reproducible, took me only 4 tries. Updated versions: OpenSearch operator: v2.6.1 OpenSearch: 2.14.0...

This is a great idea! However, I think this statement is a bit overly-optimistic: "The investigation guides contain the information needed to create the rule file". These are the issues...

EDIT: The Agent itself is now (8.18.0+) fixed and does reenroll if the token changes: https://github.com/elastic/elastic-agent/pull/6568 --- I think this issue is more complicated than it first seems: recreating the...

Also having basically the same issue just with the Elastic Agent container. There's no systemd (and thus journalctl) in that image either.

Since the system integration is probably the most commonly used one, I would argue that the elastic-agent image should also have Systemd installed. Currently the need for using the complete...

Well yeah, it's a bit blurry line. However I'm under the impression that the health of the elasticsearch resource (for example) also considers the actual cluster health. And for other...

Nice, but please note that #846 only partially addresses this issue. It (supposedly) fixes the issue with ISM templates, but not for index templates.

@swoehrl-mw I think the closing of this issue was premature, since #846 only partially addresses the problems reported, as discussed above.