[Do not merge] Convert tabs that can be applies-switch

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

@@ -249,9 +249,9 @@ Although autoscaling can scale some tiers by CPU, the primary measurement of tie
 
 Run this example API request to create a deployment with autoscaling:
 
-::::{tab-set}
+::::{applies-switch}
 
-:::{tab-item} {{ece}}
+:::{applies-item} ece:
 
 ```sh
 curl -k -X POST -H "Authorization: ApiKey $ECE_API_KEY" https://$COORDINATOR_HOST:12443/api/v1/deployments -H 'content-type: application/json' -d '
@@ -455,7 +455,7 @@ curl -k -X POST -H "Authorization: ApiKey $ECE_API_KEY" https://$COORDINATOR_HOS
 
 :::
 
-:::{tab-item} {{ech}}
+:::{applies-item} ess:
 
 ```sh
 curl -XPOST \

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

@@ -114,9 +114,9 @@ In case of ingest-optimized deployments, we maximize the number of model allocat
 
 #### Adaptive resources enabled
 
-::::{tab-set}
+::::{applies-switch}
 
-:::{tab-item} ECH, ECE
+:::{applies-item} { ess:, ece: }
 
 | Level | Allocations | Threads | vCPUs |
 | --- | --- | --- | --- |
@@ -128,7 +128,7 @@ In case of ingest-optimized deployments, we maximize the number of model allocat
 
 :::
 
-:::{tab-item} {{serverless-short}}
+:::{applies-item} serverless:
 
 | Level | Allocations | Threads | VCUs |
 | --- | --- | --- | --- |
@@ -142,9 +142,9 @@ In case of ingest-optimized deployments, we maximize the number of model allocat
 
 #### Adaptive resources disabled
 
-::::{tab-set}
+::::{applies-switch}
 
-:::{tab-item} ECH, ECE
+:::{applies-item} { ess:, ece: }
 
 | Level | Allocations | Threads | vCPUs |
 | --- | --- | --- | --- |
@@ -164,9 +164,9 @@ In case of search-optimized deployments, we maximize the number of threads. The
 
 #### Adaptive resources enabled
 
-::::{tab-set}
+::::{applies-switch}
 
-:::{tab-item} ECH, ECE
+:::{applies-item} { ess:, ece: }
 
 | Level | Allocations | Threads | vCPUs |
 | --- | --- | --- | --- |
@@ -178,7 +178,7 @@ In case of search-optimized deployments, we maximize the number of threads. The
 
 :::
 
-:::{tab-item} {{serverless-short}}
+:::{applies-item} serverless:
 
 | Level | Allocations | Threads | VCUs |
 | --- | --- | --- | --- |
@@ -192,9 +192,9 @@ In case of search-optimized deployments, we maximize the number of threads. The
 
 #### Adaptive resources disabled
 
-::::{tab-set}
+::::{applies-switch}
 
-:::{tab-item} ECH, ECE
+:::{applies-item} { ess:, ece: }
 
 | Level | Allocations | Threads | vCPUs |
 | --- | --- | --- | --- |

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

@@ -73,23 +73,23 @@ This section outlines the supported Kubernetes and {{stack}} versions for ECK. C
 
 ECK is compatible with the following Kubernetes distributions and related technologies:
 
-::::{tab-set}
+::::{applies-switch}
 
-:::{tab-item} ECK 3.2
+:::{applies-item} eck: ga 3.2+
 * Kubernetes 1.30-1.34
 * OpenShift 4.15-4.20
 * Google Kubernetes Engine (GKE), Azure Kubernetes Service (AKS), and Amazon Elastic Kubernetes Service (EKS)
 * Helm: {{eck_helm_minimum_version}}+
 :::
 
-:::{tab-item} ECK 3.1
+:::{applies-item} eck: ga =3.1
 * Kubernetes 1.29-1.33
 * OpenShift 4.15-4.19
 * Google Kubernetes Engine (GKE), Azure Kubernetes Service (AKS), and Amazon Elastic Kubernetes Service (EKS)
 * Helm: {{eck_helm_minimum_version}}+
 :::
 
-:::{tab-item} ECK 3.0
+:::{applies-item} eck: ga =3.0
 * Kubernetes 1.28-1.32
 * OpenShift 4.14-4.18
 * Google Kubernetes Engine (GKE), Azure Kubernetes Service (AKS), and Amazon Elastic Kubernetes Service (EKS)

deploy-manage/deploy/elastic-cloud/tools-apis.md

@@ -46,10 +46,9 @@ Note that some [restrictions](/deploy-manage/deploy/elastic-cloud/restrictions-k
 Refer to [{{es}} API conventions](elasticsearch://reference/elasticsearch/rest-apis/api-conventions.md) to learn about headers, request body conventions, and examples for {{es-serverless}} and {{es}} REST APIs.
 :::
 
-:::::{tab-set}
-:group: serverless-hosted
-::::{tab-item} {{serverless-short}}
-:sync: serverless
+:::::{applies-switch}
+
+::::{applies-item} serverless:
 
 The following APIs are available for {{es-serverless}} users:
 
@@ -59,8 +58,7 @@ The following APIs are available for {{es-serverless}} users:
 - [{{kib}} {{serverless-short}} APIs](https://www.elastic.co/docs/api/doc/serverless): Use these APIs to manage resources such as connectors, data views, and saved objects for your {{serverless-full}} project.
 ::::
 
-::::{tab-item} {{ech}}
-:sync: hosted
+::::{applies-item} ess:
 
 The following APIs are available for {{ech}} users:
 

deploy-manage/manage-spaces.md

@@ -51,11 +51,9 @@ The maximum number of spaces that you can have differs by deployment type:
 
 To create a space:
 
-:::::{tab-set}
-:group: stack-serverless
+:::::{applies-switch}
 
-::::{tab-item} {{serverless-short}}
-:sync: serverless
+::::{applies-item} serverless:
 
 1. Click **Create space** or select the space you want to edit.
 2. Provide:
@@ -67,8 +65,7 @@ To create a space:
 4. Save the space.
 ::::
 
-::::{tab-item} {{stack}}
-:sync: stack
+::::{applies-item} stack:
 
 1. Select **Create space** and provide a name, description, and URL identifier.
    The URL identifier is a short text string that becomes part of the {{kib}} URL when you are inside that space. {{kib}} suggests a URL identifier based on the name of your space, but you can customize the identifier to your liking. You cannot change the space identifier once you create the space.
@@ -95,8 +92,8 @@ You can edit all of the space settings you just defined at any time, except for
 
 Elastic also allows you to manage spaces using APIs:
 
-* **Serverless projects:** [Spaces API](https://www.elastic.co/docs/api/doc/serverless/operation/operation-get-spaces-space)
-* **{{stack}} deployments:** [Spaces API](https://www.elastic.co/docs/api/doc/kibana/operation/operation-post-spaces-copy-saved-objects)
+* {applies_to}`serverless:` [Spaces API](https://www.elastic.co/docs/api/doc/serverless/operation/operation-get-spaces-space)
+* {applies_to}`stack:` [Spaces API](https://www.elastic.co/docs/api/doc/kibana/operation/operation-post-spaces-copy-saved-objects)
 
 
 ## Define access to a space [spaces-control-user-access]
@@ -105,8 +102,8 @@ Users can access spaces based on the roles that they have.
 
 * Certain reserved roles can view and access all spaces by default. You can’t prevent those roles from accessing a space. Instead, you can grant different roles to your users.
 * When creating or editing a role, you can define which existing spaces that role can access, and with which permissions. Role management differs between {{stack}} deployments and serverless projects.
-  - For Serverless projects, check [Custom roles](/deploy-manage/users-roles/cloud-organization/user-roles.md).
-  - For {{stack}} deployments, check [Creating or editing a role](/deploy-manage/users-roles/cluster-or-deployment-auth/defining-roles.md).
+  - {applies_to}`serverless:` Check [Custom roles](/deploy-manage/users-roles/cloud-organization/user-roles.md).
+  - {applies_to}`stack:` Check [Creating or editing a role](/deploy-manage/users-roles/cluster-or-deployment-auth/defining-roles.md).
 
 
 If you're managing an {{stack}} deployment, then you can also assign roles and define permissions for a space from the **Permissions** tab of the space settings.

deploy-manage/monitor/stack-monitoring/kibana-monitoring-data.md

@@ -62,8 +62,8 @@ deployment:
 
 ## View monitoring data in {{kib}} [view-monitoring-data-in-kibana]
 
-:::::{tab-set}
-::::{tab-item} In ECK and self-managed
+:::::{applies-switch}
+::::{applies-item} { eck:, self: }
 
 1. Open the {{kib}} monitoring instance in your web browser.
 
@@ -79,7 +79,7 @@ deployment:
 If you are using a separate monitoring cluster, you do not need to turn on data collection. The dashboards appear when there is data in the monitoring cluster.
 :::
 ::::
-::::{tab-item} In ECH and ECE
+::::{applies-item} { ess:, ece: }
 :::{include} /deploy-manage/monitor/stack-monitoring/_snippets/cloud-monitoring-access.md
 :::
 ::::

deploy-manage/security/_snippets/cluster-comparison.md

@@ -9,11 +9,9 @@ Security feature availability varies by deployment type, with each feature havin
 
 Select your deployment type below to see what's available and how implementation responsibilities are distributed:
 
-::::{tab-set}
-:group: deployment-type
+::::{applies-switch}
 
-:::{tab-item} ECH
-:sync: cloud-hosted
+:::{applies-item} ess:
 
 | Category | Security feature | Status | Notes |
 |------------------|------------|--------------|-------------|
@@ -29,8 +27,7 @@ Select your deployment type below to see what's available and how implementation
 
 :::
 
-:::{tab-item} Serverless
-:sync: serverless
+:::{applies-item} serverless:
 
 | Category| Security feature | Status | Notes |
 |------------------|------------|--------------|-------------|
@@ -46,8 +43,7 @@ Select your deployment type below to see what's available and how implementation
 
 :::
 
-:::{tab-item} ECE
-:sync: ece
+:::{applies-item} ece:
 
 | Category| Security feature | Status | Notes |
 |------------------|------------|--------------|-------------|
@@ -63,8 +59,7 @@ Select your deployment type below to see what's available and how implementation
 
 :::
 
-:::{tab-item} ECK
-:sync: eck
+:::{applies-item} eck:
 
 | Category| Security feature | Status | Notes |
 |------------------|------------|--------------|-------------|
@@ -81,8 +76,7 @@ Select your deployment type below to see what's available and how implementation
 :::
 
 
-:::{tab-item} Self-managed
-:sync: self-managed
+:::{applies-item} self:
 
 | Category| Security feature | Status | Notes |
 |------------------|------------|--------------|-------------|

deploy-manage/security/ip-filtering-cloud.md

@@ -85,15 +85,15 @@ You can apply multiple policies to a single deployment. For {{ech}} deployments,
 
 #### From a deployment or project
 
-::::{tab-set}
-:::{tab-item} Serverless
+::::{applies-switch}
+:::{applies-item} serverless:
 1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body).
 2. On the **Serverless projects** page, select your project.
 3. Select the **Network security** tab on the left-hand side menu bar.
 4. Select **Apply policies** > **IP filter**.
 6. Choose the IP filter you want to apply and select **Apply**.
 :::
-:::{tab-item} Hosted
+:::{applies-item} ess:
 1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body).
 2. On the **Hosted deployments** page, select your deployment.
 3. Select the **Security** tab on the left-hand side menu bar.
@@ -116,18 +116,17 @@ If you want to a specific IP filter from a deployment or project, or delete the
 
 #### From your deployment or project
 
-::::{tab-set}
-:group: hosted-serverless
-:::{tab-item} Serverless project
-:sync: serverless
+::::{applies-switch}
+
+:::{applies-item} serverless:
 1. Find your project on the home page or on the **Serverless projects** page, then select **Manage** to access its settings menus.
 
     On the **Hosted deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list.
 2. On the **Network security** page, find the IP filter that you want to disconnect. 
 3. Under **Actions**, click the **Delete** icon.
 :::
-:::{tab-item} Hosted deployment
-:sync: hosted
+:::{applies-item} ess:
+
 1. Find your deployment on the home page or on the **Hosted deployments** page, then select **Manage** to access its settings menus.
 
     On the **Hosted deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list.

deploy-manage/security/logging-configuration/enabling-audit-logs.md

@@ -50,9 +50,9 @@ Audit logs are disabled by default and must be explicitly enabled.
 ::::
 
 
-::::::{tab-set}
+::::::{applies-switch}
 
-:::::{tab-item} Self-managed
+:::::{applies-item} self:
 
 **To enable audit logging in {{es}}**:
 
@@ -67,7 +67,7 @@ Audit logs are disabled by default and must be explicitly enabled.
 To learn how to consume these logs in an {{es}} cluster, refer to [](/deploy-manage/monitor/stack-monitoring/collecting-log-data-with-filebeat.md).
 :::::
 
-:::::{tab-item} {{ech}}
+:::::{applies-item} ess:
 
 To enable audit logging in an {{ech}} deployment:
 
@@ -90,7 +90,7 @@ To enable audit logging in an {{ech}} deployment:
 A plan change will run on your deployment. When it finishes, audit logs will be delivered to your monitoring deployment.
 :::::
 
-:::::{tab-item} ECE
+:::::{applies-item} ece:
 
 
 To enable audit logging in an ECE deployment:
@@ -115,7 +115,7 @@ To enable audit logging in an ECE deployment:
 A plan change will run on your deployment. When it finishes, audit logs will be delivered to your monitoring deployment.
 :::::
 
-:::::{tab-item} ECK
+:::::{applies-item} eck:
 
 
 To enable audit logging in an ECK-managed cluster, add `xpack.security.audit.enabled: true` to the `config` section of each {{es}} `nodeSet` and to the `config` section of the {{kib}} object's specification.