[deploy manage] Move images

deploy-manage/api-keys/elasticsearch-api-keys.md

@@ -15,7 +15,7 @@ Several types of {{es}} API keys exist:
 
 To manage API keys in {{kib}}, go to the **API Keys** management page using the navigation menu or the [global search field](../../explore-analyze/find-and-organize/find-apps-and-objects.md).
 
-![API Keys UI](../../images/kibana-api-keys.png "")
+![API Keys UI](/deploy-manage/images/kibana-api-keys.png "")
 
 
 ## Security privileges [api-keys-security-privileges]
@@ -33,7 +33,7 @@ To manage roles, go to the **Roles** management page using the navigation menu o
 
 To create an API key, go to the **API Keys** management page using the navigation menu or the [global search field](../../explore-analyze/find-and-organize/find-apps-and-objects.md), and select **Create API key**.
 
-![Create API Key UI](../../images/kibana-create-ccr-api-key.png "")
+![Create API Key UI](/deploy-manage/images/kibana-create-ccr-api-key.png "")
 
 Refer to the [Create API key](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-security-create-api-key) documentation to learn more about creating user API keys.
 

deploy-manage/api-keys/serverless-project-api-keys.md

@@ -14,7 +14,7 @@ In serverless projects, the following types of API keys exist:
 
 You can manage your keys in **{{project-settings}} → {{manage-app}} → {{api-keys-app}}**:
 
-:::{image} ../../images/serverless-api-key-management.png
+:::{image} /deploy-manage/images/serverless-api-key-management.png
 :alt: API keys UI
 :screenshot:
 :::
@@ -24,7 +24,7 @@ You can manage your keys in **{{project-settings}} → {{manage-app}} → {{api-
 
 In **{{api-keys-app}}**, click **Create API key**:
 
-:::{image} ../../images/serverless-create-personal-api-key.png
+:::{image} /deploy-manage/images/serverless-create-personal-api-key.png
 :alt: Create API key UI
 :screenshot:
 :width: 50%

deploy-manage/autoscaling/autoscaling-in-ece-and-ech.md

@@ -163,7 +163,7 @@ To help you better understand the available autoscaling settings, this example d
 
         The fault tolerance for the data tier is set to 2 availability zones.
 
-        :::{image} ../../images/cloud-enterprise-ec-ce-autoscaling-data-summary2.png
+        :::{image} /deploy-manage/images/cloud-enterprise-ec-ce-autoscaling-data-summary2.png
         :alt: A screenshot showing sizing information for the autoscaled data tier
         :::
 
@@ -181,7 +181,7 @@ To help you better understand the available autoscaling settings, this example d
 
         The fault tolerance for the machine learning instance is set to 1 availability zone.
 
-        :::{image} ../../images/cloud-enterprise-ec-ce-autoscaling-ml-summary2.png
+        :::{image} /deploy-manage/images/cloud-enterprise-ec-ce-autoscaling-ml-summary2.png
         :alt: A screenshot showing sizing information for the autoscaled machine learning node
         :::
 

deploy-manage/autoscaling/trained-model-autoscaling.md

@@ -70,7 +70,7 @@ You can choose from three levels of resource usage for your trained model deploy
 
 Refer to the tables in the [Model deployment resource matrix](#model-deployment-resource-matrix) section to find out the setings for the level you selected.
 
-:::{image} ../../images/machine-learning-ml-nlp-deployment-id-elser-v2.png
+:::{image} /deploy-manage/images/machine-learning-ml-nlp-deployment-id-elser-v2.png
 :alt: ELSER deployment with adaptive resources enabled.
 :screenshot:
 :width: 500px

deploy-manage/cloud-organization/billing/billing-faq.md

@@ -54,7 +54,7 @@ $$$faq-cost$$$Is there a way for me to estimate how much {{ecloud}} will cost?
 $$$faq-consumption$$$Where can I find a detailed view of my consumption?
 :   To make it easy to track the ongoing cost of {{ecloud}}, we’ve added line items to the downloadable [invoices](https://cloud.elastic.co/billing/overview?page=docs&placement=docs-body).
 
-    ![Example invoice](../../../images/cloud-ec-bill-example-new.png)
+    ![Example invoice](/deploy-manage/images/cloud-ec-bill-example-new.png)
 
     Additionally, on the {{ecloud}} [Usage](https://cloud.elastic.co/billing/usage?page=docs&placement=docs-body) page, the **Month-to-date usage** tile shows accrued costs and can help you to better estimate the next charge amount.
 

deploy-manage/deploy/cloud-enterprise/connect-elasticsearch.md

@@ -69,7 +69,7 @@ Connections through Cloud IDs are only supported in Beats and Logstash.
 
 Cloud IDs are available in every deployment page, as showed below:
 
-:::{image} ../../../images/cloud-enterprise-ec-ce-cloud-id.png
+:::{image} /deploy-manage/images/cloud-enterprise-ec-ce-cloud-id.png
 :alt: The Cloud ID and `elastic` user information shown when you create a deployment
 :::
 

deploy-manage/deploy/cloud-enterprise/create-deployment.md

@@ -18,7 +18,7 @@ To create a deployment in ECE:
 
     You can quickly create a deployment by setting the basic parameters shown in the UI. If you need more control, select **Advanced settings** to configure additional options, as detailed below.
 
-    :::{image} ../../../images/cloud-enterprise-ece-create-deployment.png
+    :::{image} /deploy-manage/images/cloud-enterprise-ece-create-deployment.png
     :alt: Create a deployment
     :::
 

deploy-manage/deploy/cloud-enterprise/customize-deployment.md

@@ -46,15 +46,15 @@ In the deployment edit page, you can configure the following settings and featur
 
     * From the **Size per zone** drop-down menu, select what best fits your requirements.
 
-        :::{image} ../../../images/cloud-enterprise-ec-customize-deployment2.png
+        :::{image} /deploy-manage/images/cloud-enterprise-ec-customize-deployment2.png
         :alt: Customize hot data and content tier nodes
         :::
 
         Based on the size you select for a tier, ECE automatically calculates the required number of nodes. Before adding additional nodes, the system scales up existing nodes to the maximum size allowed by their instance configuration, as defined in the deployment template. The maximum size for an {{es}} instance using the default templates typically ranges between 58GB and 64GB RAM.
 
         The **Architecture** summary displays the total number of nodes per zone, where each circle color represents a different node type:
 
-        :::{image} ../../../images/cloud-enterprise-ec-number-of-nodes.png
+        :::{image} /deploy-manage/images/cloud-enterprise-ec-number-of-nodes.png
         :alt: Number of nodes per deployment size
         :::
 

deploy-manage/deploy/cloud-enterprise/deploy-large-installation.md

@@ -21,7 +21,7 @@ This type of installation is recommended for deployments with significant overal
 * 3 hosts with 16 GB RAM each for proxies
 * 3 availability zones
 
-:::{image} ../../../images/cloud-enterprise-ece-pb-9.png
+:::{image} /deploy-manage/images/cloud-enterprise-ece-pb-9.png
 :alt: A large installation with nine to twelve hosts across three availability zones
 :::
 

deploy-manage/deploy/cloud-enterprise/deploy-medium-installation.md

@@ -15,7 +15,7 @@ This type of installation is recommended for many production setups. You need:
 * 3 hosts with 256 GB RAM each for allocators
 * 3 availability zones
 
-:::{image} ../../../images/cloud-enterprise-ece-pb-6.png
+:::{image} /deploy-manage/images/cloud-enterprise-ece-pb-6.png
 :alt: A medium installation with nine to twelve hosts across three availability zones
 :::
 

deploy-manage/deploy/cloud-enterprise/deploy-small-installation.md

@@ -14,7 +14,7 @@ The type of installation is recommended for development, test, and small-scale u
 * 3 hosts with 128 GB RAM
 * 3 availability zones
 
-:::{image} ../../../images/cloud-enterprise-ece-pb-3.png
+:::{image} /deploy-manage/images/cloud-enterprise-ece-pb-3.png
 :alt: A small baseline installation with three hosts across three availability zones
 :::
 

deploy-manage/deploy/cloud-enterprise/ece-architecture.md

@@ -15,7 +15,7 @@ Elastic Cloud Enterprise has a service-oriented architecture that lets you:
 * Access services through the API.
 * Deploy each service independently in its own Docker container.
 
-:::{image} ../../../images/cloud-enterprise-ece-architecture.png
+:::{image} /deploy-manage/images/cloud-enterprise-ece-architecture.png
 :alt: Elastic Cloud Enterprise high level architecture
 :::
 

deploy-manage/deploy/cloud-enterprise/ece-configuring-ece-create-templates.md

@@ -28,27 +28,27 @@ Before you start creating your own deployment templates, you should have: [tagge
 5. Select **Create template**. The **Configure instances** page opens.
 6. Choose whether or not [autoscaling](/deploy-manage/autoscaling/autoscaling-in-ece-and-ech.md) is enabled by default for deployments created using the template. Autoscaling adjusts resources available to the deployment automatically as loads change over time.
 
-    :::{image} ../../../images/cloud-enterprise-ece-create-template-autoscaling.png
+    :::{image} /deploy-manage/images/cloud-enterprise-ece-create-template-autoscaling.png
     :alt: screencapture of the "Enable autoscaling by default" switch
     :::
 
 7. Configure the initial settings for all of the data tiers and components that will be available in the template. A default is provided for every setting and you can adjust these as needed. For each data tier and component, you can:
 
     * Select which [instance configuration](ece-configuring-ece-instance-configurations-create.md) to assign to the template. This allows you to optimize the performance of your deployments by matching a machine type to a use case. A hot data and content tier, for example, is best suited to be allocated with an instance configuration having fast SSD storage, while warm and cold data tiers should be allocated with an instance configuration with larger storage but likely less performant, lower cost hardware.
 
-        :::{image} ../../../images/cloud-enterprise-ece-create-template-instance-configuration.png
+        :::{image} /deploy-manage/images/cloud-enterprise-ece-create-template-instance-configuration.png
         :alt: screencapture of the "Initial size per zone" dropdown box
         :::
 
     * Adjust the default, initial amount of memory and storage. Increasing memory and storage also improves performance by increasing the CPU resources that get assigned relative to the size of the instance, meaning that a 32 GB instance gets twice as much CPU resource as a 16 GB one. These resources are just template defaults that can be adjusted further before you create actual deployments.
 
-        :::{image} ../../../images/cloud-enterprise-ece-create-template-initial-size.png
+        :::{image} /deploy-manage/images/cloud-enterprise-ece-create-template-initial-size.png
         :alt: screencapture of the "Initial size per zone" dropdown box
         :::
 
     * Configure autoscaling settings for the deployment.
 
-        :::{image} ../../../images/cloud-enterprise-ece-create-template-max-autoscaling.png
+        :::{image} /deploy-manage/images/cloud-enterprise-ece-create-template-max-autoscaling.png
         :alt: screencapture of the "Maximum autoscaling size per zone" dropdown box
         :::
 
@@ -59,13 +59,13 @@ Before you start creating your own deployment templates, you should have: [tagge
 
     * Add [fault tolerance](ece-ha.md) (high availability) by using more than one availability zone.
 
-        :::{image} ../../../images/cloud-enterprise-ece-create-template-availability-zones.png
+        :::{image} /deploy-manage/images/cloud-enterprise-ece-create-template-availability-zones.png
         :alt: screencapture of the "Availability zones" radio buttons
         :::
 
     * Add user settings to configure how Elasticsearch and other components run. Check [Editing your user settings](edit-stack-settings.md) for details about what settings are available.
 
-        :::{image} ../../../images/cloud-enterprise-ece-create-template-user-settings.png
+        :::{image} /deploy-manage/images/cloud-enterprise-ece-create-template-user-settings.png
         :alt: screencapture of the "User settings" expandable section
         :::
 

deploy-manage/deploy/cloud-enterprise/ece-configuring-ece-instance-configurations-edit.md

@@ -42,7 +42,7 @@ If you edit instance configurations, so that they match fewer allocators, instan
 
         For example: Enter `SSD` and `true`, if you tagged your allocators with this tag, or enter whatever tag you are using to identify allocators that can host Elasticsearch data nodes for incoming data.
 
-        :::{image} ../../../images/cloud-enterprise-ece-query-ui.png
+        :::{image} /deploy-manage/images/cloud-enterprise-ece-query-ui.png
         :alt: Creating a query that filters on allocator tags
         :::
 

deploy-manage/deploy/cloud-enterprise/ece-configuring-ece-tag-allocators.md

@@ -62,7 +62,7 @@ If you have an allocator that meets several criteria, such as an allocator with
 
 4. Enter values into the **Key** and **Value** fields, and then select **Add tag**. For example: You could add `SSD: true` and `highCPU: true` tags from our [example tags](#allocator-sample-tags) if your allocator meets these criteria.
 
-    :::{image} ../../../images/cloud-enterprise-ece-tagging-ui.png
+    :::{image} /deploy-manage/images/cloud-enterprise-ece-tagging-ui.png
     :alt: Adding key-value pairs as an allocator tags
     :::
 

deploy-manage/deploy/cloud-enterprise/ece-networking-prereq.md

@@ -21,7 +21,7 @@ For versions 2.4.0 and 2.4.1, IPv6 should remain enabled on any host with the Pr
 
 When there are multiple hosts for each role, the inbound networking and ports can be represented by the following diagram:
 
-![ECE networking and ports](../../../images/cloud-enterprise-ece-networking-ports.png "")
+![ECE networking and ports](/deploy-manage/images/cloud-enterprise-ece-networking-ports.png "")
 
 | **Number** | **Host role** | **Inbound ports** | *Purpose* |
 | --- | --- | --- | --- |

deploy-manage/deploy/cloud-enterprise/identify-deployment-scenario.md

@@ -18,7 +18,7 @@ The type of deployment is recommended for development, test, and small-scale use
 * 3 hosts with 128 GB RAM
 * 3 availability zones
 
-:::{image} ../../../images/cloud-enterprise-ece-pb-3.png
+:::{image} /deploy-manage/images/cloud-enterprise-ece-pb-3.png
 :alt: A small baseline installation with three hosts across three availability zones
 :::
 
@@ -42,7 +42,7 @@ This type of deployment is recommended for many production setups. You need:
 * 3 hosts with 16 GB RAM each for proxies
 * 3 availability zones
 
-:::{image} ../../../images/cloud-enterprise-ece-pb-6.png
+:::{image} /deploy-manage/images/cloud-enterprise-ece-pb-6.png
 :alt: A medium installation with nine to twelve hosts across three availability zones
 :::
 
@@ -65,7 +65,7 @@ This type of deployment is recommended for deployments with significant overall
 * 3 hosts with 16 GB RAM each for proxies
 * 3 availability zones
 
-:::{image} ../../../images/cloud-enterprise-ece-pb-9.png
+:::{image} /deploy-manage/images/cloud-enterprise-ece-pb-9.png
 :alt: A large installation with nine to twelve hosts across three availability zones
 :::
 

deploy-manage/deploy/cloud-enterprise/keep-track-of-deployment-activity.md

@@ -25,7 +25,7 @@ To view the activity for a deployment:
     3. Select one of the resource filters to view activity for only that resource type.
 
 
-:::{image} ../../../images/cloud-enterprise-ec-ce-activity-page.png
+:::{image} /deploy-manage/images/cloud-enterprise-ec-ce-activity-page.png
 :alt: The Activity page
 :::
 

deploy-manage/deploy/cloud-enterprise/migrate-ece-to-podman-hosts.md

@@ -21,7 +21,7 @@ Using Docker or Podman as container runtime is a configuration local to the host
 ::::
 
 
-:::{image} ../../../images/cloud-enterprise-podman-migration-overview-1.png
+:::{image} /deploy-manage/images/cloud-enterprise-podman-migration-overview-1.png
 :alt: Migration Overview
 :::
 
@@ -42,13 +42,13 @@ Using Docker or Podman as container runtime is a configuration local to the host
 
     **Example 1** You want to migrate the Docker host `192.168.44.74` with the role `Allocator` to a podman host. Copy the role `allocator`.
 
-    :::{image} ../../../images/cloud-enterprise-podman-migration-fetch-roles-1.png
+    :::{image} /deploy-manage/images/cloud-enterprise-podman-migration-fetch-roles-1.png
     :alt: Migrate Allocator
     :::
 
     **Example 2** You want to migrate the Docker host `192.168.44.10` with the roles `Allocator`, `Controller`, `Director`, and `Proxy` to a podman host. Copy the roles `allocator`, `coordinator`, `director`, `proxy`.
 
-    :::{image} ../../../images/cloud-enterprise-podman-migration-fetch-roles-2.png
+    :::{image} /deploy-manage/images/cloud-enterprise-podman-migration-fetch-roles-2.png
     :alt: Migrate Allocator
     :::
 
@@ -423,13 +423,13 @@ Using Docker or Podman as container runtime is a configuration local to the host
 
         The following screenshot shows the state where the correct roles have been applied. Both hosts in ece-zone-1 have the same color.
 
-        :::{image} ../../../images/cloud-enterprise-podman-migration-correct-role-1.png
+        :::{image} /deploy-manage/images/cloud-enterprise-podman-migration-correct-role-1.png
         :alt: Correct role
         :::
 
         The following screenshot shows the state where incorrect roles have been applied. The hosts in ece-zone-1 do not have the same coloring.
 
-        :::{image} ../../../images/cloud-enterprise-podman-migration-wrong-role-1.png
+        :::{image} /deploy-manage/images/cloud-enterprise-podman-migration-wrong-role-1.png
         :alt: Wrong role
         :::
 
@@ -449,7 +449,7 @@ Using Docker or Podman as container runtime is a configuration local to the host
         ::::
 
 
-        :::{image} ../../../images/cloud-enterprise-podman-migration-move-instances-1.png
+        :::{image} /deploy-manage/images/cloud-enterprise-podman-migration-move-instances-1.png
         :alt: Move instances
         :::
 

deploy-manage/deploy/cloud-enterprise/search-filter-deployments.md

@@ -16,7 +16,7 @@ The **Deployments** page in the Cloud UI provides several ways to find deploymen
 * Search for partial or whole deployment names or IDs in the search text box
 * Add filters to the **Deployments** view to filter for specific conditions:
 
-    :::{image} ../../../images/cloud-enterprise-deployment-filter.png
+    :::{image} /deploy-manage/images/cloud-enterprise-deployment-filter.png
     :alt: Add a filter
     :::
 

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

@@ -323,7 +323,7 @@ To avoid this, explicitly define the requests and limits mandated by your enviro
 
 [Metricbeat](beats.md) can collect the percentage of both the CPU and the memory limits used by each Pod (or total node allocatable if resource is not limited). The two relevant metrics are `kubernetes.pod.cpu.usage.limit.pct` for CPU, and `kubernetes.pod.memory.usage.node.pct` for memory.
 
-:::{image} ../../../images/cloud-on-k8s-metrics-explorer-cpu.png
+:::{image} /deploy-manage/images/cloud-on-k8s-metrics-explorer-cpu.png
 :alt: cgroup CPU perforamce chart
 :screenshot:
 :::
@@ -353,7 +353,7 @@ nodeSets:
 
 The **Cgroup usage** curve shows that the CPU usage of this container has been steadily increasing up to 2 cores. Then, while the container was still requesting more CPU, the **Cgroup Throttling** curve shows how much the Elasticsearch container has been throttled:
 
-:::{image} ../../../images/cloud-on-k8s-cgroups-cfs-stats.png
+:::{image} /deploy-manage/images/cloud-on-k8s-cgroups-cfs-stats.png
 :alt: cgroup CPU perforamce chart
 :screenshot:
 :::