Peter Brachwitz

I stepped into a trap when testing this yesterday by using one of our existing manifests with the `-e` option and only with @thbkrkr 's help was able to identify...

Is this bug still present given that we have made significant changes to how the status is calculated?

When you (mis-)configure Elasticsearch with a file realm secret that does not exist you should see two things: * a log entry in the operator log with the message `referenced...

> Please let me know and I'll make the changes, and see what they look like. I don't have something that is ready to implement. I feel like Agent is...

I think we have a similar issue with the `elasticsearch.k8s.elastic.co/cluster-uuid` annotation which will also happen right away incrementing the generation and making any subsequent status updates fail with a conflict

1. I think I am in favour of keeping the CRD separate, for the same reasons that @anyasabo has mentioned. We are are bit uncertain about the future of this...

The default value for `allocation_delay` is still 5 minutes. I realise that the documentation I linked to in the comment does not (no longer?) mention that but the code is...

There is an open bug in Elasticsearch where shards in the cold tier start relocating even though the `allocation_delay` timeout has not yet expired. I would also be good to...

I think this is an Elasticsearch bug. I was able to reproduce your issue and have raised https://github.com/elastic/elasticsearch/issues/85922

I have created another issue because it seems that the shorter re-allocation delay is caused by the operator deleting the node shutdown records too early and Elasticsearch falling back to...