Upgrading ECKedit

Upgrading to ECK 1.0.0 from previous versionsedit

ECK 1.0.0 is largely compatible with the beta version of the operator (see the exceptions for earlier Kubernetes and OpenShift versions). There is not a direct upgrade path from the alpha version.

To upgrade from 1.0.0-beta1, follow the Quickstart. Note that all Elasticsearch and Kibana Pods go through a rolling restart when the operator is upgraded.

After the upgrade, use the v1 API version for all Elastic manifests.

See the 1.0.0 release highlights for more information on new features.

Upgrades in earlier Kubernetes and OpenShift versionsedit

Upgrading from ECK 1.0.0-beta1 to 1.0.0 has some special considerations for users running either: - Kubernetes versions < 1.13 - OpenShift 3.11

In this case, ECK must be uninstalled and reinstalled (due to an upstream bug that was not backported). To uninstall ECK, see Uninstalling ECK. Then you can follow the Quickstart to install anew. You can save your existing v1beta1 manifests, update them to the v1 API version, take snapshots and restore them as well.

After the upgrade, use the v1 API version for all Elastic manifests.