From ec156fc5f49e027a7d00993024e2be4e4bb090ab Mon Sep 17 00:00:00 2001 From: david-kow <50632861+david-kow@users.noreply.github.com> Date: Wed, 15 Jan 2020 09:27:32 +0100 Subject: [PATCH] Add mention about Kibana pods restarting during ECK upgrade (#2422) (#2428) * Add mention about Kibana pods restarting during ECK upgrade * Remove duplicated paragraph --- docs/upgrading-eck.asciidoc | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/docs/upgrading-eck.asciidoc b/docs/upgrading-eck.asciidoc index b467dbc13c..94e9b9585e 100644 --- a/docs/upgrading-eck.asciidoc +++ b/docs/upgrading-eck.asciidoc @@ -12,7 +12,7 @@ endif::[] ECK 1.0.0 is largely compatible with the beta version of the operator (see <<{p}-ga-openshift,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 <<{p}-quickstart>>. Note that all Elasticsearch Pods go through a rolling restart when the operator is upgraded. +To upgrade from 1.0.0-beta1, follow the <<{p}-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. @@ -26,8 +26,6 @@ Upgrading from ECK 1.0.0-beta1 to 1.0.0 has some special considerations for user - Kubernetes versions < 1.13 - OpenShift 3.11 -In this case, ECK must be uninstalled and reinstalled (due to link:https://github.com/kubernetes/kubernetes/issues/73752[an upstream bug] that was not backported). To uninstall ECK, see <<{p}-uninstalling-eck>>. Then you can follow the <<{p}-quickstart>> to install anew. You may wish to save your existing `v1beta1` manifests and update them to the `v1` API version, and to <<{p}-snapshots,take snapshots>> and restore them as well. - In this case, ECK must be uninstalled and reinstalled (due to link:https://github.com/kubernetes/kubernetes/issues/73752[an upstream bug] that was not backported). To uninstall ECK, see <<{p}-uninstalling-eck>>. Then you can follow the <<{p}-quickstart>> to install anew. You can save your existing `v1beta1` manifests, update them to the `v1` API version, <<{p}-snapshots,take snapshots>> and restore them as well. After the upgrade, use the `v1` API version for all Elastic manifests.