Merge branch 'main' into ts-obs-applies

Author: natasha-moore-elastic

deploy-manage/deploy/cloud-on-k8s.md

@@ -68,7 +68,7 @@ This section outlines the supported Kubernetes and Elastic Stack versions for EC
 ECK is compatible with the following Kubernetes distributions and related technologies:
 
 * Kubernetes 1.28-1.32
-* OpenShift 4.13-4.18
+* OpenShift 4.14-4.18
 * Google Kubernetes Engine (GKE), Azure Kubernetes Service (AKS), and Amazon Elastic Kubernetes Service (EKS)
 * Helm: 3.2.0+
 

deploy-manage/deploy/elastic-cloud/change-hardware.md

@@ -24,6 +24,12 @@ Prerequisites:
 Follow these steps to migrate to a different instance configuration, replacing the default `$EC_API_KEY` value with your actual API key:
 
 1. From the  [list of instance configurations available for each region](asciidocalypse://docs/cloud/docs/reference/cloud-hosted/ec-regions-templates-instances.md), select the target instance configuration you want to migrate to.
+
+   ::::{note}
+   The target instance configuration must be compatible with the Elasticsearch tier or stateless resource you are updating. 
+   For example, if you are migrating the hot Elasticsearch tier, the target instance configuration must also be of the `es.datahot` family.
+   ::::
+
 2. Get the deployment update payload from the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body) **Edit** page, by selecting **Equivalent API request**, and store it in a file called `migrate_instance_configuration.json`.
 
     Example payload containing relevant data for migrating the hot Elasticsearch tier:

deploy-manage/upgrade/deployment-or-cluster.md

@@ -11,7 +11,6 @@ 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/cloud-on-k8s/current/k8s-orchestration.html
 ---
 
 # Upgrade your deployment or cluster
@@ -34,7 +33,6 @@ mapped_urls:
 % - [ ] ./raw-migrated-files/stack-docs/elastic-stack/upgrade-elastic-stack-for-elastic-cloud.md
 % - [ ] ./raw-migrated-files/stack-docs/elastic-stack/upgrading-elastic-stack-on-prem.md
 % - [ ] ./raw-migrated-files/cloud-on-k8s/cloud-on-k8s/k8s-upgrading-stack.md
-% - [ ] ./raw-migrated-files/cloud-on-k8s/cloud-on-k8s/k8s-orchestration.md
 %      Notes: upgrade explanations
 
 % Internal links rely on the following IDs being on this page (e.g. as a heading ID, paragraph ID, etc):
@@ -72,4 +70,5 @@ $$$upgrading-reindex$$$
 * [/raw-migrated-files/stack-docs/elastic-stack/upgrade-elastic-stack-for-elastic-cloud.md](/raw-migrated-files/stack-docs/elastic-stack/upgrade-elastic-stack-for-elastic-cloud.md)
 * [/raw-migrated-files/stack-docs/elastic-stack/upgrading-elastic-stack-on-prem.md](/raw-migrated-files/stack-docs/elastic-stack/upgrading-elastic-stack-on-prem.md)
 * [/raw-migrated-files/cloud-on-k8s/cloud-on-k8s/k8s-upgrading-stack.md](/raw-migrated-files/cloud-on-k8s/cloud-on-k8s/k8s-upgrading-stack.md)
-* [/raw-migrated-files/cloud-on-k8s/cloud-on-k8s/k8s-orchestration.md](/raw-migrated-files/cloud-on-k8s/cloud-on-k8s/k8s-orchestration.md)
+
+% EEDUGON note: when working on this document, or in the ECK upgrade documentation we should include a link to [nodes orchestration](../deploy/cloud-on-k8s/nodes-orchestration.md) as reference to learn the details on how ECK orchestates / manages the upgrade of the individual instances.