Peter Brachwitz

Closing this as this is not a bug in the ECK operator but a limitation of the how Elasticsearch upgrades work and there is not automated remediation of the described...

There is a 2x. release series now as well.

Can you share your Heartbeat configuration? We are testing Heartbeat daily with this configuration on OpenShift: https://github.com/elastic/cloud-on-k8s/blob/1577f2debad821b86bb18d24385066a989c0935a/test/e2e/beat/config.go#L67-L78 and I am trying to understand what is different in your use case.

Idea: install kyverno in all dev/CI environments (should be mostly already the case), add a policy that prevents us from using the built-in GKE storage classes. Create our own storage...

Live migrating from a Helm chart managed cluster is currently not supported. This is due to the way how ECK exclusively manages the cluster/master node quorum/transport x509 certificates. Your options...

> I see that at least for Filebeat, there is number of [inputs](https://www.elastic.co/guide/en/beats/filebeat/master/configuration-filebeat-options.html) that support pushing to the Beat: HTTP Endpoint, HTTP JSON, NetFlow, Syslog, TCP, UDP. [HTTP JSON](https://www.elastic.co/guide/en/beats/filebeat/master/filebeat-input-httpjson.html) does...

As @barkbay has pointed out the issue here is that even if we were to allow multiple config policies that the resulting configuration still needs to fit into a single...

Reading through this I don't see a specific need for a code change. The PDB fix for the single node clusters has been merged. So I am tempted to make...

Why is this only now an issue? Or did we just not notice before?

We need to make this version specific as this metricset seems to exist only since 8.7