Merge branch 'main' into index-template-doc-priority

Author: leemthompo

deploy-manage/deploy/self-managed/_snippets/etc-elasticsearch.md

@@ -4,7 +4,13 @@ The `setgid` flag applies group permissions on the `/etc/elasticsearch` director
 
 {{es}} loads its configuration from the `/etc/elasticsearch/elasticsearch.yml` file by default. The format of this config file is explained in [](/deploy-manage/deploy/self-managed/configure-elasticsearch.md).
 
-The {{distro}} package also has a system configuration file (`/etc/sysconfig/elasticsearch`), which allows you to set the following parameters:
+The {{distro}} package also has a system configuration file at the following path:
+ 
+```txt subs=true
+{{pkg-conf}}
+```
+
+In this file, you can set the following parameters:
 
 | Parameter | Description |
 | --- | --- |
@@ -14,5 +20,5 @@ The {{distro}} package also has a system configuration file (`/etc/sysconfig/ela
 | `RESTART_ON_UPGRADE` | Configure restart on package upgrade, defaults to `false`. This means you will have to restart your {{es}} instance after installing a package  manually. The reason for this is to ensure, that upgrades in a cluster do not result in a continuous shard reallocation resulting in high network traffic and reducing the response times of your cluster. |
 
 ::::{note}
-Distributions that use `systemd` require that system resource limits be configured via `systemd` rather than via the `/etc/sysconfig/elasticsearch` file. See [Systemd configuration](/deploy-manage/deploy/self-managed/setting-system-settings.md#systemd) for more information.
+Distributions that use `systemd` require that system resource limits be configured via `systemd` rather than via the {{pkg-conf}} file. See [Systemd configuration](/deploy-manage/deploy/self-managed/setting-system-settings.md#systemd) for more information.
 ::::

deploy-manage/deploy/self-managed/install-elasticsearch-with-debian-package.md

@@ -13,6 +13,7 @@ sub:
   distro: Debian
   export: "export "
   escape: \
+  pkg-conf: /etc/default/elasticsearch
 ---
 
 # Install {{es}} with a Debian package [deb]

deploy-manage/deploy/self-managed/install-elasticsearch-with-rpm.md

@@ -12,6 +12,7 @@ sub:
   slash: /
   distro: RPM
   export: export
+  pkg-conf: /etc/sysconfig/elasticsearch
 ---
 
 # Install {{es}} with RPM [rpm]

deploy-manage/upgrade/orchestrator/upgrade-cloud-enterprise.md

@@ -94,7 +94,7 @@ Before starting the upgrade process, verify that your setup meets the following
   :::
 
   - Ensure that your system deployments are at their [expected versions](/deploy-manage/deploy/cloud-enterprise/default-system-deployment-versions.md). Since ECE 3.6.1, the upgrade process automatically upgrades system deployments to the required version. If the {{ece}} platform was upgraded successfully and yet one or more system deployments were not upgraded to [their expected version](/deploy-manage/deploy/cloud-enterprise/default-system-deployment-versions.md) during the very last phase of the {{ece}} upgrade, you can re-run the `elastic-cloud-enterprise.sh upgrade --cloud-enterprise-version <your target version>` command to retry system deployment upgrade only.
-  - Check that your deployments are running on {{stack}} version 7.0.0 or above.
+  - Check that your deployments are running on {{stack}} version 8.0.0 or above.
 - Before running the upgrade command, ensure that you include the same installation flags that were used during the initial setup. Some deployment configurations, such as those using Podman or SELinux, require specific flags to be passed again during the upgrade. Failure to do so may result in compatibility errors.
 
 ## Certificate rotation [ece-upgrade-certificates]