Peter Brachwitz

> Is there some needed documentation to transition between the 2 states? I think the important part when transitioning from one state to the other is to keep the CA...

> In order to document a working example should we add that issuer to the snippet? Yes I think that's a good idea.

I added a bit to the docs to make the self-signed issuer explicit in https://github.com/elastic/cloud-on-k8s/pull/7925/commits/ef8386bf13d5cb53fb4debe78223068eb9809468

@cmacknz could you help us assess what the problem might be? It is an older version of the stack, 8.1.3, that we are testing here that might have known issues....

It looks like OOM is at least responsible for some of the failures. In https://github.com/elastic/cloud-on-k8s/pull/8021 I bumped the memory to `640Mi` now which at least in the builds I ran...

@barkbay I agree with all of your points above. While browsing our documentation recently I found these instructions: https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-common-problems.html#k8s-common-problems-scale-down They are currently targeted to one specific problem but the workaround...

I removed my previous post. I cut off the routing table in a bad place. There was still a shard assigned.

A possible workaround that we are currently considering to add through the operator directly in #8380 by default is an additional `emptyDir` volume in the logs mount path. For example...

Good catch. My mistake. Will update the example.

Thanks @afharo that's a good point we currently do not set `max-old-space-size` at all in ECK. And we are not using the ECH stack packs but rather the default Kibana...