diff --git a/deploy-manage/toc.yml b/deploy-manage/toc.yml index c15beec91c..4582f3d70a 100644 --- a/deploy-manage/toc.yml +++ b/deploy-manage/toc.yml @@ -804,8 +804,7 @@ toc: - file: upgrade/orchestrator/upgrade-cloud-on-k8s.md - file: upgrade/prepare-to-upgrade.md children: - - file: upgrade/prepare-to-upgrade/upgrade-assistant.md - - file: upgrade/prepare-to-upgrade/index-compatibility.md + - file: upgrade/prepare-to-upgrade/upgrade-assistant.md - file: upgrade/deployment-or-cluster.md children: - file: upgrade/deployment-or-cluster/upgrade-on-ech.md diff --git a/deploy-manage/upgrade/deployment-or-cluster.md b/deploy-manage/upgrade/deployment-or-cluster.md index 84a54edecc..a58c369010 100644 --- a/deploy-manage/upgrade/deployment-or-cluster.md +++ b/deploy-manage/upgrade/deployment-or-cluster.md @@ -10,6 +10,7 @@ mapped_urls: - https://www.elastic.co/guide/en/elastic-stack/current/upgrade-elastic-stack-for-elastic-cloud.html - https://www.elastic.co/guide/en/elastic-stack/current/upgrading-elastic-stack-on-prem.html - https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-upgrading-stack.html + - https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-upgrade.html --- diff --git a/deploy-manage/upgrade/prepare-to-upgrade/index-compatibility.md b/deploy-manage/upgrade/prepare-to-upgrade/index-compatibility.md deleted file mode 100644 index 682782adae..0000000000 --- a/deploy-manage/upgrade/prepare-to-upgrade/index-compatibility.md +++ /dev/null @@ -1,39 +0,0 @@ ---- -mapped_pages: - - https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-upgrade.html ---- - -# Index compatibility [setup-upgrade] - -::::{important} -:name: upgrade-pre-release - -This documentation is for {{es}} 9.0.0-beta1, which is not yet released. You can upgrade from a previously released version to a pre-release build, if following a supported upgrade path. Upgrading from a pre-release build to any other build is not supported, and can result in errors or silent data loss. If you run a pre-release build for testing, discard the contents of the cluster before upgrading to another build of {{es}}. -:::: - - -{{es}} clusters can usually be upgraded one node at a time so upgrading does not interrupt service. For upgrade instructions, refer to [Upgrading to Elastic 9.0.0-beta1](../deployment-or-cluster.md). - -::::{admonition} Upgrade from 7.x -:class: important - -To upgrade to 9.0.0-beta1 from 7.16 or an earlier version, **you must first upgrade to 8.17**, even if you opt to do a full-cluster restart instead of a rolling upgrade. This enables you to use the **Upgrade Assistant** to identify and resolve issues, reindex indices created before 7.0, and then perform a rolling upgrade. You must resolve all critical issues before proceeding with the upgrade. For instructions, refer to [Prepare to upgrade from 7.x](../deployment-or-cluster.md#prepare-to-upgrade). -:::: - - - -## Index compatibility [upgrade-index-compatibility] - -{{es}} has full query and write support for indices created in the previous major version. If you have indices created in 6.x or earlier, you might use the [archive functionality](../deployment-or-cluster/reading-indices-from-older-elasticsearch-versions.md) to import them into newer {{es}} versions, or you must reindex or delete them before upgrading to 9.0.0-beta1. {{es}} nodes will fail to start if incompatible indices are present. Snapshots of 6.x or earlier indices can only restored using the [archive functionality](../deployment-or-cluster/reading-indices-from-older-elasticsearch-versions.md) to a 8.x cluster even if they were created by a 7.x cluster. The **Upgrade Assistant** in 8.17 identifies any indices that need to be reindexed or removed. - - -## REST API compatibility [upgrade-rest-api-compatibility] - -[REST API compatibility](elasticsearch://reference/elasticsearch/rest-apis/compatibility.md) is a per-request opt-in feature that can help REST clients mitigate non-compatible (breaking) changes to the REST API. - - -## FIPS Compliance and Java 17 [upgrade-fips-java17] - -{{es}} 8.0+ requires Java 17 or later. {{es}} 8.13+ has been tested with [Bouncy Castle](https://www.bouncycastle.org/java.html)'s Java 17 [certified](https://csrc.nist.gov/projects/cryptographic-module-validation-program/certificate/4616) FIPS implementation and is the recommended Java security provider when running {{es}} in FIPS 140-2 mode. Note - {{es}} does not ship with a FIPS certified security provider and requires explicit installation and configuration. - -Alternatively, consider using {{ech}} in the [FedRAMP-certified GovCloud region](https://www.elastic.co/industries/public-sector/fedramp). diff --git a/troubleshoot/deployments/cloud-on-k8s/common-problems.md b/troubleshoot/deployments/cloud-on-k8s/common-problems.md index 2f16eb94f1..9c7c6348ee 100644 --- a/troubleshoot/deployments/cloud-on-k8s/common-problems.md +++ b/troubleshoot/deployments/cloud-on-k8s/common-problems.md @@ -244,7 +244,7 @@ If you are using one of the affected versions of OLM and upgrading OLM to a newe ## If you upgraded Elasticsearch to the wrong version [k8s-common-problems-version-downgrade] -If you accidentally upgrade one of your Elasticsearch clusters to a version that does not exist or a version to which a direct upgrade is not possible from your currently deployed version, a validation will prevent you from going back to the previous version. The reason for this validation is that ECK will not allow downgrades as this is not supported by Elasticsearch and once the data directory of Elasticsearch has been upgraded there is no way back to the old version without a [snapshot restore](/deploy-manage/upgrade/prepare-to-upgrade/index-compatibility.md). +If you accidentally upgrade one of your Elasticsearch clusters to a version that does not exist or a version to which a direct upgrade is not possible from your currently deployed version, a validation will prevent you from going back to the previous version. The reason for this validation is that ECK will not allow downgrades as this is not supported by Elasticsearch and once the data directory of Elasticsearch has been upgraded there is no way back to the old version without a [snapshot restore](/deploy-manage/tools/snapshot-and-restore.md). These two upgrading scenarios, however, are exceptions because Elasticsearch never started up successfully. If you annotate the Elasticsearch resource with `eck.k8s.elastic.co/disable-downgrade-validation=true` ECK allows you to go back to the old version at your own risk. If you also attempted an upgrade of other related Elastic Stack applications at the same time you can use the same annotation to go back. Remove the annotation afterwards to prevent accidental downgrades and reduced availability.