Elastic Cloud Enterprise 3.5.1

The following changes are included in this release.

New --force-upgrade CLI argument for ECE upgrader. The elastic-cloud-enterprise.sh upgrade command now has a --force-upgrade option. It’s useful when a previous attempt at upgrading the ECE platform failed for technical reasons and re-attempting it results in the upgrade monitor process "hanging" forever (for example, waiting for an upgrade step to complete on a runner that’s not online anymore) or otherwise failing. Note that after a previous failed upgrade attempt, the frc-upgraders-monitor must be manually removed by running docker rm -f frc-upgraders-monitor.

The --force-upgrade parameter also lets you run the ECE upgrade even if the platform is already at the desired target version (useful in situations where, for instance, a container failed to upgrade to the target version).

ECE upgrader: automatically update stale beats config. ECE upgrader now automatically ensures that filebeat, metricbeat and adminconsole configurations contain the up-to-date logging-and-metrics cluster ID. This check is performed regardless of the version ECE is being upgraded to. It’s helpful in situations where the logging-and-metrics cluster is removed and replaced with a new one.

Incorporate cluster_uuid into Proxy to detect clusters in split state more accurately. For Elasticsearch versions 7.x and higher, Proxy will refer to the now-available cluster_uuid field to determine whether the cluster is in a split state. For earlier versions, Proxy will continue to refer to the presence of multiple master node IDs.

Add step to remove route-server certs on disk prior to recreating route-server and restarting proxy. Update certificate rotation script to remove proxy/route-server certificates on disk when they are expiring to allow newly created certs to be written back to disk upon route-server start-up.