Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
florent-leborgne wants to merge 10 commits into
base: main
Choose a base branch
from
Open

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

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
10 commits
Select commit Hold shift + click to select a range
42d194f
convert some tabs into applies-switch
florent-leborgne Dec 19, 2025
cbde482
typo
florent-leborgne Dec 19, 2025
dd13a1a
Merge branch 'main' into convert-tabs-into-applies-switch
florent-leborgne Dec 19, 2025
c9689e7
fixes
florent-leborgne Dec 19, 2025
d435b94
simplify
florent-leborgne Dec 19, 2025
95af9b4
fix
florent-leborgne Dec 19, 2025
3837b66
the right fixes
florent-leborgne Dec 19, 2025
ca36768
Merge branch 'main' into convert-tabs-into-applies-switch
florent-leborgne Dec 19, 2025
80a0851
another missed one
florent-leborgne Dec 19, 2025
187086e
Merge branch 'convert-tabs-into-applies-switch' of github.com:florent…
florent-leborgne Dec 19, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions deploy-manage/autoscaling/autoscaling-in-ece-and-ech.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 '
Expand Down Expand Up @@ -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 \
Expand Down
20 changes: 10 additions & 10 deletions deploy-manage/autoscaling/trained-model-autoscaling.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 |
| --- | --- | --- | --- |
Expand All @@ -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 |
| --- | --- | --- | --- |
Expand All @@ -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: }
Comment on lines 143 to +147
Copy link
Collaborator

@shainaraskas shainaraskas Dec 22, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think a one-tab applies switch is an anti-pattern. this should be a tag on the section instead.


| Level | Allocations | Threads | vCPUs |
| --- | --- | --- | --- |
Expand All @@ -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 |
| --- | --- | --- | --- |
Expand All @@ -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 |
| --- | --- | --- | --- |
Expand All @@ -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 |
| --- | --- | --- | --- |
Expand Down
8 changes: 4 additions & 4 deletions deploy-manage/deploy/cloud-on-k8s.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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)
Expand Down
10 changes: 4 additions & 6 deletions deploy-manage/deploy/elastic-cloud/tools-apis.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:

Expand All @@ -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:

Expand Down
17 changes: 7 additions & 10 deletions deploy-manage/manage-spaces.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand All @@ -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.
Expand All @@ -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)
Comment on lines +95 to +96
Copy link
Collaborator

@shainaraskas shainaraskas Dec 22, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think this is a good case for applies tags because it's harder to read



## Define access to a space [spaces-control-user-access]
Expand All @@ -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.
Expand Down
6 changes: 3 additions & 3 deletions deploy-manage/monitor/stack-monitoring/kibana-monitoring-data.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand All @@ -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
:::
::::
Expand Down
18 changes: 6 additions & 12 deletions deploy-manage/security/_snippets/cluster-comparison.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 |
|------------------|------------|--------------|-------------|
Expand All @@ -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 |
|------------------|------------|--------------|-------------|
Expand All @@ -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 |
|------------------|------------|--------------|-------------|
Expand All @@ -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 |
|------------------|------------|--------------|-------------|
Expand All @@ -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 |
|------------------|------------|--------------|-------------|
Expand Down
17 changes: 8 additions & 9 deletions deploy-manage/security/ip-filtering-cloud.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand All @@ -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.
Expand Down
10 changes: 5 additions & 5 deletions deploy-manage/security/logging-configuration/enabling-audit-logs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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}}**:

Expand All @@ -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:

Expand All @@ -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:
Expand All @@ -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.
Expand Down
Loading
Loading