Merge branch 'main' into central-config-pg

Author: shainaraskas

.github/workflows/add-new-team-label.yml

@@ -0,0 +1,18 @@
+name: "Label new issues with needs-team"
+
+on:
+  issues:
+    types: [opened]
+
+jobs:
+  add-needs-triage-label:
+    name: Add `needs-team` label
+    runs-on: ubuntu-latest
+    steps:
+      - name: Add the needs-team label
+        uses: actions-ecosystem/action-add-labels@v1
+        with:
+          labels: |
+            needs-team
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/add-to-board.yml

@@ -0,0 +1,43 @@
+name: Triage & route issues
+
+on:
+  issues:
+    types: [labeled]
+
+permissions:
+  issues: write
+  contents: read
+
+jobs:
+  route:
+    runs-on: ubuntu-latest
+    if: |
+      github.event.label.name == 'team:DocsEng' ||
+      github.event.label.name == 'team:Obs' ||
+      github.event.label.name == 'team:Platform' ||
+      github.event.label.name == 'team:Projects' ||
+      github.event.label.name == 'team:Search' ||
+      github.event.label.name == 'team:Security'
+    env:
+      PROJECT_ID_MAP: |
+        {
+          "team:DocsEng":   "1625",
+          "team:Obs":       "649",
+          "team:Platform":  "1232",
+          "team:Projects":  "1415",
+          "team:Search":    "726",
+          "team:Security":  "1034"
+        }
+    steps:
+      - name: Remove needs-team label
+        uses: actions-ecosystem/action-remove-labels@v1
+        with:
+          labels: needs-team
+
+      - name: Add issue to the right project
+        uses: actions/add-to-project@244f685bbc3b7adfa8466e08b698b5577571133e
+        with:
+          project-url: https://github.com/orgs/elastic/projects/${{ fromJson(env.PROJECT_ID_MAP)[github.event.label.name] }}
+          github-token: ${{ secrets.ADD_TO_BOARD_TOKEN }}
+          labeled: ${{ github.event.label.name }}
+          label-operator: OR

deploy-manage/autoscaling/autoscaling-in-eck.md

@@ -20,6 +20,14 @@ Configure autoscaling for {{es}} deployments in {{eck}}. Learn how to enable aut
 
 ECK can leverage the [autoscaling API](https://www.elastic.co/docs/api/doc/elasticsearch/group/endpoint-autoscaling) introduced in {{es}} 7.11 to adjust automatically the number of Pods and the allocated resources in a tier. Currently, autoscaling is supported for {{es}} [data tiers](/manage-data/lifecycle/data-tiers.md) and machine learning nodes.
 
+### Supported Resources for Autoscaling per Elasticsearch Tier
+
+| Tiers | Storage | Memory | CPU |
+| --- | ---| --- | --- |
+| Data Nodes (except Frozen) | Yes | Calculated proportionally to the required amount of storage | Calculated proportionally to the required amount of memory
+| Frozen Nodes | Yes | Yes | Calculated proportionally to the required amount of memory
+| Machine Learning | No | Yes | Calculated proportionally to the required amount of memory
+
 
 ### Enable autoscaling [k8s-enable]
 
@@ -345,4 +353,4 @@ spec:
         target:
           type: Utilization
           averageUtilization: 50
-```
+```

deploy-manage/cloud-organization/billing/elasticsearch-billing-dimensions.md

@@ -40,7 +40,7 @@ For detailed {{es-serverless}} project rates, see the [{{es-serverless}} pricing
 You can control costs using the following strategies:
 
 * **Search Power setting:** [Search Power](../../deploy/elastic-cloud/project-settings.md#elasticsearch-manage-project-search-power-settings) controls the speed of searches against your data. With Search Power, you can improve search performance by adding more resources for querying, or you can reduce provisioned resources to cut costs.
-* **Time series data retention:** By limiting the number of days of [time series data](../../../solutions/search/ingest-for-search.md#elasticsearch-ingest-time-series-data) that are available for caching, you can reduce the number of search VCUs required.
+* **Search boost window**: By limiting the number of days of [time series data](../../../solutions/search/ingest-for-search.md#elasticsearch-ingest-time-series-data) that are available for caching, you can reduce the number of search VCUs required.
 * **Machine learning trained model autoscaling:** Configure your trained model deployment to allow it to scale down to zero allocations when there are no active inference requests:
 
     * When starting or updating a trained model deployment, [Enable adaptive resources](../../autoscaling/trained-model-autoscaling.md#enabling-autoscaling-in-kibana-adaptive-resources) and set the VCU usage level to **Low**.

deploy-manage/cloud-organization/service-status.md

@@ -17,15 +17,15 @@ applies_to:
 
 {{ech}} deployments and Serverless projects run on different cloud platforms, such as Amazon Web Services (AWS),  Google Cloud Platform (GCP), and Microsoft Azure. Like any service, it might undergo availability changes from time to time. When availability changes, Elastic makes sure to provide you with a current service status.
 
-To check current and past service availability, go to to the [Cloud Status](https://cloud-status.elastic.co/) page. Services are separated into {{ech}} services and [Serverless services](https://status.elastic.co/?section=serverless).
+To check current and past service availability, go to to the [Cloud Status](https://status.elastic.co/) page. Services are separated into {{ech}} services and [Serverless services](https://status.elastic.co/?section=serverless).
 
 ## Subscribe to updates [ec_subscribe_to_updates]
 
 Don’t want to check the service status page manually? You can get notified about changes to the service status automatically.
 
 To receive service status updates:
 
-1. Go to the [Cloud Status](https://cloud-status.elastic.co/) page and select **SUBSCRIBE TO UPDATES**.
+1. Go to the [Cloud Status](https://status.elastic.co/) page and select **SUBSCRIBE TO UPDATES**.
 2. Select one of the following methods to be notified of status updates:
 
     * Email
@@ -38,7 +38,7 @@ After you subscribe to updates, you are notified whenever a service status updat
 
 If you want to know about specific status updates, rather than all of them, you can adjust your preferences by using the following steps. These steps apply to both new signups and adjustments to an existing subscription.
 
-Go to the [Cloud Status](https://cloud-status.elastic.co/) page and select **SUBSCRIBE TO UPDATES**. Enter your email address and click **SUBSCRIBE VIA EMAIL**. You will be brought to a page with a list of regions and components.
+Go to the [Cloud Status](https://status.elastic.co/) page and select **SUBSCRIBE TO UPDATES**. Enter your email address and click **SUBSCRIBE VIA EMAIL**. You will be brought to a page with a list of regions and components.
 
 Here, you can customize your selections as needed, and then click **Save**.
 

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

@@ -14,6 +14,10 @@ Note that since version 2.7.0, system deployments are automatically upgraded whe
 
 | {{ece}} version | Admin cluster | Logging & Metrics cluster | Security cluster |
 | --- | --- | --- | --- |
+| 4.0.0 | 8.18.0 | 8.18.0 | 8.18.0 |
+| 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 |
 | 3.7.1 | 7.17.20 | 7.17.20 | 8.13.2 |
 | 3.6.2 | 7.17.15 | 7.17.15 | 8.11.1 |
 | 3.6.1 | 7.17.13 | 7.17.13 | 8.9.2 |

deploy-manage/deploy/self-managed/_snippets/check-es-running.md

@@ -1,7 +1,7 @@
 You can test that your {{es}} node is running by sending an HTTPS request to port `9200` on `localhost`:
 
 ```sh subs=true
-curl --cacert {{es-conf}}{{slash}}certs{{slash}}http_ca.crt {{escape}} <1>
+curl --cacert {{es-conf}}{{slash}}certs{{slash}}http_ca.crt <1>
 -u elastic:$ELASTIC_PASSWORD https://localhost:9200 <2>
 ```
 1. `--cacert`: Path to the generated `http_ca.crt` certificate for the HTTP layer.
@@ -29,4 +29,4 @@ The call returns a response like this:
   },
   "tagline" : "You Know, for Search"
 }
-```
+```

deploy-manage/deploy/self-managed/_snippets/pw-env-var.md

@@ -1,9 +1,9 @@
 We recommend storing the `elastic` password as an environment variable in your shell. For example:
 
 ```sh subs=true
-{{export}}ELASTIC_PASSWORD="your_password"
+{{export}} ELASTIC_PASSWORD="your_password"
 ```
 
 If you have password-protected the {{es}} keystore, you will be prompted to enter the keystore’s password. See [Secure settings](/deploy-manage/security/secure-settings.md) for more details.
 
-To learn how to reset this password, refer to [](/deploy-manage/users-roles/cluster-or-deployment-auth/built-in-sm.md).
+To learn how to reset this password, refer to [](/deploy-manage/users-roles/cluster-or-deployment-auth/built-in-sm.md).

deploy-manage/security/supported-ssltls-versions-by-jdk-version.md

@@ -24,20 +24,16 @@ Check your security provider’s release notes for information on TLS support.
 :   SSL v3 is supported on all {{es}} [compatible JDKs](../deploy/self-managed/installing-elasticsearch.md#jvm-version) but is disabled by default. See [Enabling additional SSL/TLS versions on your JDK](#jdk-enable-tls-protocol).
 
 `TLSv1`
-:   TLS v1.0 is supported on all {{es}} [compatible JDKs](../deploy/self-managed/installing-elasticsearch.md#jvm-version). Some newer JDKs, including the JDK bundled with {{es}}, disable TLS v1.0 by default. See [Enabling additional SSL/TLS versions on your JDK](#jdk-enable-tls-protocol).
+:   TLS v1.0 is supported on all {{es}} [compatible JDKs](../deploy/self-managed/installing-elasticsearch.md#jvm-version) but is disabled by default. See [Enabling additional SSL/TLS versions on your JDK](#jdk-enable-tls-protocol).
 
 `TLSv1.1`
-:   TLS v1.1 is supported on all {{es}} [compatible JDKs](../deploy/self-managed/installing-elasticsearch.md#jvm-version). Some newer JDKs, including the JDK bundled with {{es}}, disable TLS v1.1 by default. See [Enabling additional SSL/TLS versions on your JDK](#jdk-enable-tls-protocol).
+:   TLS v1.1 is supported on all {{es}} [compatible JDKs](../deploy/self-managed/installing-elasticsearch.md#jvm-version) but is disabled by default. See [Enabling additional SSL/TLS versions on your JDK](#jdk-enable-tls-protocol).
 
 `TLSv1.2`
 :   TLS v1.2 is supported on all {{es}} [compatible JDKs](../deploy/self-managed/installing-elasticsearch.md#jvm-version). It is enabled by default on all JDKs that are supported by {{es}}, including the bundled JDK.
 
 `TLSv1.3`
-:   TLS v1.3 is supported on JDK11 and later, and JDK8 builds newer than 8u261 (including the most recent release of each JDK8 distribution that {{es}} supports). TLS v1.3 is supported and enabled by default on the JDK that is bundled with {{es}}.
-
-    ::::{note}
-    Although {{es}} supports running on older JDK8 builds without TLS v1.3, we recommend upgrading to a JDK version that includes TLS v1.3 for better support and updates.
-    ::::
+:   TLS v1.3 is supported on all {{es}} [compatible JDKs](../deploy/self-managed/installing-elasticsearch.md#jvm-version). It is enabled by default on all JDKs that are supported by {{es}}, including the bundled JDK.
 
 
 ## Enabling additional SSL/TLS versions on your JDK [jdk-enable-tls-protocol]
@@ -59,10 +55,6 @@ For the {{es}} **bundled JDK**, the configuration file is in a sub directory of
 * Windows: `$ES_HOME/jdk/conf/security/java.security`
 * macOS:`$ES_HOME/jdk.app/Contents/Home/conf/security/java.security`
 
-For **JDK8**, the configuration file is within the `jre/lib/security` directory of the Java installation. If `$JAVA_HOME` points to the home directory of the JDK that you use to run {{es}}, then the configuration file will be in:
-
-* `$JAVA_HOME/jre/lib/security/java.security`
-
 For **JDK11 or later**, the configuration file is within the `conf/security` directory of the Java installation. If `$JAVA_HOME` points to the home directory of the JDK that you use to run {{es}}, then the configuration file will be in:
 
 * `$JAVA_HOME/conf/security/java.security`
@@ -72,11 +64,12 @@ For **JDK11 or later**, the configuration file is within the `conf/security` dir
 
 Within the JDK configuration file is a line that starts with `jdk.tls.disabledAlgorithms=`. This setting controls which protocols and algorithms are *disabled* in your JDK. The value of that setting will typically span multiple lines.
 
-For example, in OpenJDK 16 the setting is:
+For example, in OpenJDK 21 the setting is:
 
 ```text
-jdk.tls.disabledAlgorithms=SSLv3, TLSv1, TLSv1.1, RC4, DES, MD5withRSA, \
-    DH keySize < 1024, EC keySize < 224, 3DES_EDE_CBC, anon, NULL
+jdk.tls.disabledAlgorithms=SSLv3, TLSv1, TLSv1.1, DTLSv1.0, RC4, DES, \
+    MD5withRSA, DH keySize < 1024, EC keySize < 224, 3DES_EDE_CBC, anon, NULL, \
+    ECDH
 ```
 
 Create a new file in your in your {{es}} configuration directory named `es.java.security`. Copy the `jdk.tls.disabledAlgorithms` setting from the JDK’s default configuration file into `es.java.security`. You do not need to copy any other settings.
@@ -86,11 +79,12 @@ Create a new file in your in your {{es}} configuration directory named `es.java.
 
 Edit the `es.java.security` file in your {{es}} configuration directory, and modify the `jdk.tls.disabledAlgorithms` setting so that any SSL or TLS versions that you wish to use are no longer listed.
 
-For example, to enable TLSv1.1 on OpenJDK 16 (which uses the `jdk.tls.disabledAlgorithms` settings shown previously), the `es.java.security` file would contain the previously disabled TLS algorithms *except* `TLSv1.1`:
+For example, to enable TLSv1.1 on OpenJDK 21 (which uses the `jdk.tls.disabledAlgorithms` settings shown previously), the `es.java.security` file would contain the previously disabled TLS algorithms *except* `TLSv1.1`:
 
 ```text
-jdk.tls.disabledAlgorithms=SSLv3, TLSv1, RC4, DES, MD5withRSA, \
-    DH keySize < 1024, EC keySize < 224, 3DES_EDE_CBC, anon, NULL
+jdk.tls.disabledAlgorithms=SSLv3, TLSv1, DTLSv1.0, RC4, DES, \
+    MD5withRSA, DH keySize < 1024, EC keySize < 224, 3DES_EDE_CBC, anon, NULL, \
+    ECDH
 ```
 
 

deploy-manage/tools/snapshot-and-restore/read-only-url-repository.md

@@ -42,7 +42,7 @@ PUT _snapshot/my_read_only_url_repository
 :   (Optional, Boolean) If `true`, metadata files, such as index mappings and settings, are compressed in snapshots. Data files are not compressed. Defaults to `true`.
 
 `max_number_of_snapshots`
-:   (Optional, integer) Maximum number of snapshots the repository can contain. Defaults to `Integer.MAX_VALUE`, which is `2^31-1` or `2147483647`.
+:   (Optional, integer) Maximum number of snapshots the repository can contain. Defaults to `Integer.MAX_VALUE`, which is `2`^`31`^`-1` or `2147483647`.
 
 `max_restore_bytes_per_sec`
 :   (Optional, [byte value](elasticsearch://reference/elasticsearch/rest-apis/api-conventions.md#byte-units)) Maximum snapshot restore rate per node. Defaults to unlimited. Note that restores are also throttled through [recovery settings](elasticsearch://reference/elasticsearch/configuration-reference/index-recovery-settings.md).