Michael Morello

I'm closing this issue because my feeling is that your questions are more related to Fleet itself than to the operator. I would suggest to open a new topic in...

> I expected the elasticsearch pod to start with an initContainer elastic-internal-init-filesystem which would prepare the mounted PVC for the data directory (elasticsearch-data) with the correct ownership and octal permissions....

> I have upgraded Elasticsearch version successfully, but the PHASE is still ApplyingChanges. Is there anything in the operator's logs that would explain what the operator is trying to reconcile?

Closing due to inactivity, feel free to reopen if needed.

How do know that the problem comes from `thread_pool.write.size`? I'm asking because other issues are known to generate the same error: https://github.com/elastic/elasticsearch/pull/96138 I want to double check that it is...

>However, it looks like that eck-operator is considering the nodes with less CPU allocated in the cluster [...] The configuration is rejected by Elasticsearch. The operator submits the configuration, but...

Could you please check that you are not in the same situation as described in https://github.com/elastic/cloud-on-k8s/issues/1705 This seems to be an "environmental issue", unrelated to ECK itself. If not could...

> This doesn't work. I deployed an Elasticsearch resource named `elasticsearch`, and then used you example on ECK `2.10.0`. It seems to be working as expected: ```bash > helm upgrade...

As a side note I also successfully got Kibana running using the `eck-stack` chart: ``` > helm upgrade -i test-kb -n foo --values should-not-work.yaml $ECK/deploy/eck-stack/ Release "test-kb" does not exist....

I'm wondering if we could stop reconciling that `Secret` if we [use a CSI driver to manage the certificates](https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-transport-settings.html#k8s-transport-third-party-tools) for example? (Or give an option to the user skip the...