Merge branch 'main' into autoops-vs-stack-monitoring

Author: wajihaparvez

.github/workflows/doc-preview-comment.yml

@@ -0,0 +1,77 @@
+name: "Docs preview comment"
+
+on:
+  pull_request_target:
+    types: [opened, reopened, synchronize]
+
+permissions:
+  contents: read
+  issues: write
+  pull-requests: write
+
+jobs:
+  preview-links:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Comment preview links for changed docs
+        uses: actions/github-script@v7
+        with:
+          github-token: ${{ secrets.GITHUB_TOKEN }}
+          script: |
+            const pr     = context.payload.pull_request;
+            const prNum  = pr.number;
+            const owner  = context.repo.owner;
+            const repo   = context.repo.repo;
+            const base   = `https://docs-v3-preview.elastic.dev/${owner}/${repo}/pull/${prNum}`;
+
+            // 1) List all files in this PR
+            const { data: files } = await github.rest.pulls.listFiles({
+              owner, repo, pull_number: prNum
+            });
+
+            // 2) Filter to only added/modified .md files (skip removed and _snippets/)
+            const links = files
+              .filter(f =>
+                f.status !== 'removed' &&
+                /\.md$/i.test(f.filename) &&
+                !/(^|\/)_snippets\//i.test(f.filename)
+              )
+              .map(f => {
+                let p = f.filename.replace(/\/index\.md$/i, '/');
+                if (p === f.filename) p = p.replace(/\.md$/i, '');
+                return `- [\`${f.filename}\`](${base}/${p})`;
+              });
+
+            if (!links.length) return;  // nothing to do
+
+            // 3) Build the comment body
+            const body = [
+              "🔍 **Preview links for changed docs:**",
+              "",
+              ...links,
+              "",
+              "🔔 *The preview site may take up to **3 minutes** to finish building. These links will become live once it completes.*"
+            ].join("\n");
+
+            // 4) Post or update a single bot comment
+            const { data: comments } = await github.rest.issues.listComments({
+              owner, repo, issue_number: prNum
+            });
+            const existing = comments.find(c =>
+              c.user.type === 'Bot' &&
+              c.body.startsWith("🔍 **Preview links for changed docs:**")
+            );
+
+            if (existing) {
+              await github.rest.issues.updateComment({
+                owner, repo,
+                comment_id: existing.id,
+                body
+              });
+            } else {
+              await github.rest.issues.createComment({
+                owner, repo,
+                issue_number: prNum,
+                body
+              });
+            }

deploy-manage/deploy/cloud-enterprise/configure-host-rhel.md

@@ -12,13 +12,10 @@ products:
 
 # Configure a RHEL host [ece-configure-hosts-rhel-centos]
 
-
-
 The following instructions show you how to prepare your hosts on Red Hat Enterprise Linux 8 (RHEL 8), 9 (RHEL 9), and Rocky Linux 8 and 9.
 
 * [Prerequisites](#ece-prerequisites-rhel8)
-* [Configure the host](#ece-configure-hosts-rhel8-podman)
-
+* [Install Podman and configure the host](#ece-configure-hosts-rhel8-podman)
 
 ## Prerequisites [ece-prerequisites-rhel8]
 
@@ -28,7 +25,11 @@ Verify that required traffic is allowed. Check the [Networking prerequisites](ec
 
 **Example:** For AWS, allowing traffic between hosts is implemented using security groups.
 
-## Configure the host [ece-configure-hosts-rhel8-podman]
+::::{important}
+Make sure to use a supported combination of Linux distribution and container engine version as defined in our official [Support matrix](https://www.elastic.co/support/matrix#elastic-cloud-enterprise). Unsupported combinations can lead to various issues in your ECE environment, including failures when creating system deployments, upgrading workload deployments, proxy timeouts, and more.
+::::
+
+## Install Podman and configure the host [ece-configure-hosts-rhel8-podman]
 
 1. Install the OS packages `lvm2`, `iptables`, `sysstat`, and `net-tools` by executing:
 

deploy-manage/deploy/cloud-enterprise/configure-host-suse.md

@@ -12,10 +12,10 @@ products:
 
 # Configure a SUSE host [ece-configure-hosts-sles12]
 
-The following instructions show you how to prepare your hosts on SLES 12 SP5 or 15.
+The following instructions explain how to prepare your hosts on SUSE Linux Enterprise Server 12 SP5 (SLES 12) or 15 (SLES 15).
 
 * [Install Docker](#ece-install-docker-sles12)
-* [Set up XFS on SLES](#ece-xfs-setup-sles12)
+* [Set up XFS quotas](#ece-xfs-setup-sles12)
 * [Update the configurations settings](#ece-update-config-sles)
 * [Configure the Docker daemon options](#ece-configure-docker-daemon-sles12)
 
@@ -26,11 +26,10 @@ If you want to install {{ece}} (ECE) on your own hosts, the steps for preparing
 
 Regardless of which approach you take, the steps in this section need to be performed on every host that you want to use with ECE.
 
-
-## Install Docker [ece-install-docker-sles12]
+## Install Docker on SLES [ece-install-docker-sles12]
 
 ::::{important}
-Make sure to use a combination of Linux distribution and Docker version that is supported, following our official [Support matrix](https://www.elastic.co/support/matrix#elastic-cloud-enterprise). Using unsupported combinations can cause multiple issues with you ECE environment, such as failures to create system deployments, to upgrade workload deployments, proxy timeouts, and more.
+Make sure to use a supported combination of Linux distribution and container engine version as defined in our official [Support matrix](https://www.elastic.co/support/matrix#elastic-cloud-enterprise). Unsupported combinations can lead to various issues in your ECE environment, including failures when creating system deployments, upgrading workload deployments, proxy timeouts, and more.
 ::::
 
 
@@ -87,7 +86,7 @@ Make sure to use a combination of Linux distribution and Docker version that is
 
 
 
-## Set up XFS on SLES [ece-xfs-setup-sles12]
+## Set up XFS quotas [ece-xfs-setup-sles12]
 
 XFS is required to support disk space quotas for {{es}} data directories. Some Linux distributions such as RHEL and Rocky Linux already provide XFS as the default file system. On SLES 12 and 15, you need to set up an XFS file system and have quotas enabled.
 

deploy-manage/deploy/cloud-enterprise/configure-host-ubuntu.md

@@ -12,25 +12,20 @@ products:
 
 # Configure an Ubuntu host [ece-configure-hosts-ubuntu]
 
-The following instructions show you how to prepare your hosts on 20.04 LTS (Focal Fossa) and Ubuntu 22.04 LTS (Jammy Jellyfish).
+The following instructions show you how to prepare your hosts on Ubuntu.
 
-* [Install Docker 24.0](#ece-install-docker-ubuntu)
+* [Install Docker](#ece-install-docker-ubuntu)
 * [Set up XFS quotas](#ece-xfs-setup-ubuntu)
 * [Update the configurations settings](#ece-update-config-ubuntu)
 * [Configure the Docker daemon options](#ece-configure-docker-daemon-ubuntu)
 
 
-## Install Docker [ece-install-docker-ubuntu]
+## Install Docker on Ubuntu [ece-install-docker-ubuntu]
 
-Install Docker LTS version 24.0 for Ubuntu 20.04 or 22.04.
+Install a compatible Docker version on Ubuntu.
 
 ::::{important}
-Make sure to use a combination of Linux distribution and Docker version that is supported, following our official [Support matrix](https://www.elastic.co/support/matrix#elastic-cloud-enterprise). Using unsupported combinations can cause multiple issues with you ECE environment, such as failures to create system deployments, to upgrade workload deployments, proxy timeouts, and more.
-::::
-
-
-::::{note}
-Docker 25 and higher are not compatible with ECE 3.7.
+Make sure to use a supported combination of Linux distribution and container engine version as defined in our official [Support matrix](https://www.elastic.co/support/matrix#elastic-cloud-enterprise). Unsupported combinations can lead to various issues in your ECE environment, including failures when creating system deployments, upgrading workload deployments, proxy timeouts, and more.
 ::::
 
 
@@ -55,10 +50,10 @@ Docker 25 and higher are not compatible with ECE 3.7.
       $(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null
     ```
 
-4. Install the correct version of the `docker-ce` package, for Ubuntu 20.04 LTS (Focal Fossa) or Ubuntu 22.04 LTS (Jammy Jellyfish):
+4. Install the correct version of the `docker-ce` package. The following is an example of installing Docker 27.0. If you decide to install a different Docker version, make sure to replace with the desired version in the commands below.
 
     ```sh
-    sudo apt install -y docker-ce=5:24.0.* docker-ce-cli=5:24.0.* containerd.io
+    sudo apt install -y docker-ce=5:27.0.* docker-ce-cli=5:27.0.* containerd.io
     ```
 
 

deploy-manage/deploy/cloud-enterprise/configure-operating-system.md

@@ -13,7 +13,10 @@ products:
 
 Before installing {{ece}}, you have to prepare your hosts with one of the following Linux distributions:
 
-* [Ubuntu 20.04 LTS (Focal Fossa) and Ubuntu 22.04 LTS (Jammy Jellyfish)](configure-host-ubuntu.md)
-* [Red Hat Enterprise Linux (RHEL) 8 and 9](configure-host-rhel.md)
-* [Rocky Linux 8 and 9](configure-host-rhel.md)
-* [SUSE Linux Enterprise Server (SLES) 12 SP5 and 15](configure-host-suse.md)
+* [Ubuntu](configure-host-ubuntu.md)
+* [Red Hat Enterprise Linux (RHEL) and Rocky Linux](configure-host-rhel.md)
+* [SUSE Linux Enterprise Server (SLES)](configure-host-suse.md)
+
+::::{important}
+Make sure to use a supported combination of Linux distribution and container engine version, such as `Docker` or `Podman`, as defined in our official [Support matrix](https://www.elastic.co/support/matrix#elastic-cloud-enterprise). Unsupported combinations can lead to various issues in your ECE environment, including failures when creating system deployments, upgrading workload deployments, proxy timeouts, and more.
+::::

deploy-manage/deploy/cloud-enterprise/default-system-deployment-versions.md

@@ -16,7 +16,9 @@ Note that since version 2.7.0, system deployments are automatically upgraded whe
 
 | {{ece}} version | Admin cluster | Logging & Metrics cluster | Security cluster |
 | --- | --- | --- | --- |
+| 4.0.1 | 8.18.0 | 8.18.0 | 8.18.0 |
 | 4.0.0 | 8.18.0 | 8.18.0 | 8.18.0 |
+| 3.8.1 | 8.17.4 | 8.17.4 | 8.17.4 |
 | 3.8.0 | 8.17.4 | 8.17.4 | 8.17.4 |
 | 3.7.3 | 7.17.24 | 7.17.24 | 8.15.2 |
 | 3.7.2 | 7.17.22 | 7.17.22 | 8.13.4 |

deploy-manage/deploy/cloud-enterprise/ece-install-offline-images.md

@@ -14,9 +14,9 @@ Versions of the {{stack}}, containing {{es}}, {{kib}}, and other products, are a
 
 The first table contains the stack versions that shipped with the 4.0 version of {{ece}}. You can also check the [most recent stack packs and Docker images](#ece-recent-download-list), which might have released after the 4.0 version of ECE, as well as the [full list of available stack packs and Docker images](#ece-full-download-list).
 
-| Docker images included with {{ece}} 4.0.0 |
+| Docker images included with {{ece}} 4.0.1 |
 | --- |
-| docker.elastic.co/cloud-enterprise/elastic-cloud-enterprise:4.0.0 |
+| docker.elastic.co/cloud-enterprise/elastic-cloud-enterprise:4.0.1 |
 | docker.elastic.co/cloud-release/elasticsearch-cloud-ess:8.18.0 |
 | docker.elastic.co/cloud-release/kibana-cloud:8.18.0 |
 | docker.elastic.co/cloud-release/elastic-agent-cloud:8.18.0 |

deploy-manage/deploy/cloud-enterprise/ece-install-offline-no-registry.md

@@ -16,7 +16,7 @@ To perform an offline installation without a private Docker registry, you have t
 1. On an internet-connected host that has Docker installed, download the [Available Docker Images](ece-install-offline-images.md). Note that for ECE version 4.0, if you want to use {{stack}} version 9.0 in your deployments, you need to download and make available both the version 8.x and version 9.x Docker images (the version 8.x images are required for system deployments).
 
     ```sh
-    docker pull docker.elastic.co/cloud-enterprise/elastic-cloud-enterprise:4.0.0
+    docker pull docker.elastic.co/cloud-enterprise/elastic-cloud-enterprise:4.0.1
     docker pull docker.elastic.co/cloud-release/elasticsearch-cloud-ess:8.18.0
     docker pull docker.elastic.co/cloud-release/kibana-cloud:8.18.0
     docker pull docker.elastic.co/cloud-release/elastic-agent-cloud:8.18.0
@@ -26,15 +26,15 @@ To perform an offline installation without a private Docker registry, you have t
     docker pull docker.elastic.co/cloud-release/elastic-agent-cloud:9.0.0
     ```
 
-    For example, for {{ece}} 4.0.0 and the {{stack}} versions it shipped with, you need:
+    For example, for {{ece}} 4.0.1 and the {{stack}} versions it shipped with, you need:
 
-    * {{ece}} 4.0.0
+    * {{ece}} 4.0.1
     * {{es}} 9.0.0, {{kib}} 9.0.0, and APM 9.0.0
 
 2. Create .tar files of the images:
 
     ```sh
-    docker save -o ece.4.0.0.tar docker.elastic.co/cloud-enterprise/elastic-cloud-enterprise:4.0.0
+    docker save -o ece.4.0.1.tar docker.elastic.co/cloud-enterprise/elastic-cloud-enterprise:4.0.1
     docker save -o es.8.18.0.tar docker.elastic.co/cloud-release/elasticsearch-cloud-ess:8.18.0
     docker save -o kibana.8.18.0.tar docker.elastic.co/cloud-release/kibana-cloud:8.18.0
     docker save -o apm.8.18.0.tar docker.elastic.co/cloud-release/elastic-agent-cloud:8.18.0
@@ -48,7 +48,7 @@ To perform an offline installation without a private Docker registry, you have t
 4. On each host, load the images into Docker, replacing `FILE_PATH` with the correct path to the .tar files:
 
     ```sh
-    docker load < FILE_PATH/ece.4.0.0.tar
+    docker load < FILE_PATH/ece.4.0.1.tar
     docker load < FILE_PATH/es.8.18.0.tar
     docker load < FILE_PATH/kibana.8.18.0.tar
     docker load < FILE_PATH/apm.8.18.0.tar

deploy-manage/deploy/cloud-enterprise/ece-install-offline-with-registry.md

@@ -22,7 +22,7 @@ Installing ECE on multiple hosts with your own registry server is simpler, becau
 2. On an internet-connected host that has Docker installed, download the [Available Docker Images](ece-install-offline-images.md) and push them to your private Docker registry. Note that for ECE version 4.0, if you want to use {{stack}} version 9.0 in your deployments, you need to download and make available both the version 8.x and version 9.x Docker images.
 
     ```sh
-    docker pull docker.elastic.co/cloud-enterprise/elastic-cloud-enterprise:4.0.0
+    docker pull docker.elastic.co/cloud-enterprise/elastic-cloud-enterprise:4.0.1
     docker pull docker.elastic.co/cloud-release/elasticsearch-cloud-ess:8.18.0
     docker pull docker.elastic.co/cloud-release/kibana-cloud:8.18.0
     docker pull docker.elastic.co/cloud-release/elastic-agent-cloud:8.18.0
@@ -32,9 +32,9 @@ Installing ECE on multiple hosts with your own registry server is simpler, becau
     docker pull docker.elastic.co/cloud-release/elastic-agent-cloud:9.0.0
     ```
 
-    For example, for {{ece}} 4.0.0 and the {{stack}} versions it shipped with, you need:
+    For example, for {{ece}} 4.0.1 and the {{stack}} versions it shipped with, you need:
 
-    * {{ece}} 4.0.0
+    * {{ece}} 4.0.1
     * {{es}} 9.0.0, {{kib}} 9.0.0, APM 9.0.0
 
     :::{important}
@@ -44,7 +44,7 @@ Installing ECE on multiple hosts with your own registry server is simpler, becau
 3. Tag the Docker images with your private registry URL by replacing `REGISTRY` with your actual registry address, for example `my.private.repo:5000`:
 
     ```sh
-    docker tag docker.elastic.co/cloud-enterprise/elastic-cloud-enterprise:4.0.0 REGISTRY/cloud-enterprise/elastic-cloud-enterprise:4.0.0
+    docker tag docker.elastic.co/cloud-enterprise/elastic-cloud-enterprise:4.0.1 REGISTRY/cloud-enterprise/elastic-cloud-enterprise:4.0.1
     docker tag docker.elastic.co/cloud-release/elasticsearch-cloud-ess:8.18.0 REGISTRY/cloud-release/elasticsearch-cloud-ess:8.18.0
     docker tag docker.elastic.co/cloud-release/kibana-cloud:8.18.0 REGISTRY/cloud-release/kibana-cloud:8.18.0
     docker tag docker.elastic.co/cloud-release/elastic-agent-cloud:8.18.0 REGISTRY/cloud-release/elastic-agent-cloud:8.18.0
@@ -57,7 +57,7 @@ Installing ECE on multiple hosts with your own registry server is simpler, becau
 4. Push the Docker images to your private Docker registry, using the same tags from the previous step. Replace `REGISTRY` with your actual registry URL, for example `my.private.repo:5000`:
 
     ```sh
-    docker push REGISTRY/cloud-enterprise/elastic-cloud-enterprise:4.0.0
+    docker push REGISTRY/cloud-enterprise/elastic-cloud-enterprise:4.0.1
     docker push REGISTRY/cloud-release/elasticsearch-cloud-ess:8.18.0
     docker push REGISTRY/cloud-release/kibana-cloud:8.18.0
     docker push REGISTRY/cloud-release/elastic-agent-cloud:8.18.0

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

@@ -31,23 +31,26 @@ ECE does not support hot-adding of resources to a running node.  When increasing
 ::::
 
 
-To adjust the allocator capacity, prior to ECE 3.5.0; it is necessary to reinstall ECE on the host with a new value assigned to the `--capacity` parameter. From ECE 3.5.0 onwards, just use the ECE API :
+To adjust the allocator capacity prior to ECE 3.5.0, you must reinstall ECE on the host with a new value assigned to the `--capacity` parameter. Starting with ECE 3.5.0, you can update the allocator capacity using the [allocator settings ECE API](https://www.elastic.co/docs/api/doc/cloud-enterprise/operation/operation-set-allocator-settings). After making this change, you must restart the allocator service for it to take effect.
 
 ```sh
 curl -X PUT \
   http(s)://<ece_admin_url:port>/api/v1/platform/infrastructure/allocators/<allocator_id>/settings \
-  -H “Authorization: ApiKey $ECE_API_KEY” \
+  -H “Authorization: ApiKey $ECE_API_KEY” \ <1>
   -H 'Content-Type: application/json' \
   -d '{"capacity":<Capacity_Value_in_MB>}'
 ```
-
-For more information on how to use API keys for authentication, check the section [Access the API from the Command Line](cloud://reference/cloud-enterprise/ece-api-command-line.md).
+1. For information on how to use API keys for authentication, refer to [Access the API from the command line](cloud://reference/cloud-enterprise/ece-api-command-line.md).
 
 ::::{important}
-Prior to ECE 3.5.0, regardless of the use of this API, the [CPU quota](#ece-alloc-cpu) used the memory specified at installation time.
+When running ECE on Podman, CPU quotas for existing instances cannot be disabled or updated. As a result, changing an allocator’s capacity won’t affect the CPU quotas of already running containers.
 ::::
 
+After applying the change, log in to the allocator host you updated and restart the allocator service:
 
+```sh
+docker restart frc-allocators-allocator
+```
 
 ### Examples [ece_examples]
 
@@ -67,6 +70,9 @@ ECE uses CPU quotas to assign shares of the allocator host to the instances that
 
 `CPU quota = DeploymentRAM / HostCapacity`
 
+::::{important}
+In ECE versions prior to 3.5.0, the CPU quota is always calculated using the memory specified at installation time, even if you later update the host capacity using the API.
+::::
 
 ### Examples [ece_examples_2]