Skip to content

Extra snippets added to remote clusters #3713

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

Merged
merged 2 commits into from
Oct 29, 2025
Merged

Extra snippets added to remote clusters #3713

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1881d41
extra snippets added
eedugon Oct 29, 2025
e4f5436
Merge branch 'main' into remote_clusters_snippets3
eedugon Oct 29, 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
1 change: 1 addition & 0 deletions deploy-manage/remote-clusters/_snippets/apikeys-local-config-intro.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
The API key created previously will be used by the local deployment to authenticate with the corresponding set of permissions to the remote deployment. For that, you need to add the API key to the local deployment's keystore.
2 changes: 2 additions & 0 deletions deploy-manage/remote-clusters/_snippets/apikeys-prerequisites-limitations.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@
* The local and remote deployments must be on {{stack}} 8.14 or later.
* Contrary to the certificate security model, the API key security model does not require that both local and remote clusters trust each other.
7 changes: 4 additions & 3 deletions deploy-manage/remote-clusters/ec-remote-cluster-ece.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,8 +34,8 @@ If network security filters are applied to the remote cluster on ECE, the remote

### Prerequisites and limitations [ec_prerequisites_and_limitations_3]

* The local and remote deployments must be on {{stack}} 8.14 or later.
* Contrary to the certificate security model, the API key security model does not require that both local and remote clusters trust each other.
:::{include} _snippets/apikeys-prerequisites-limitations.md
:::


### Create a cross-cluster API key on the remote deployment [ec_create_a_cross_cluster_api_key_on_the_remote_deployment_3]
Expand All @@ -46,7 +46,8 @@ If network security filters are applied to the remote cluster on ECE, the remote

### Configure the local deployment [ec_configure_the_local_deployment]

The API key created previously will be used by the local deployment to authenticate with the corresponding set of permissions to the remote deployment. For that, you need to add the API key to the local deployment’s keystore.
:::{include} _snippets/apikeys-local-config-intro.md
:::

The steps to follow depend on whether the Certificate Authority (CA) of the remote ECE environment’s proxy or load balancing infrastructure is public or private.

Expand Down
7 changes: 4 additions & 3 deletions deploy-manage/remote-clusters/ec-remote-cluster-other-ess.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,8 +34,8 @@ If network security policies are applied to the remote cluster, the remote clust

### Prerequisites and limitations [ec_prerequisites_and_limitations_2]

* The local and remote deployments must be on {{stack}} 8.14 or later.
* Contrary to the certificate security model, the API key security model does not require that both local and remote clusters trust each other.
:::{include} _snippets/apikeys-prerequisites-limitations.md
:::


### Create a cross-cluster API key on the remote deployment [ec_create_a_cross_cluster_api_key_on_the_remote_deployment_2]
Expand All @@ -45,7 +45,8 @@ If network security policies are applied to the remote cluster, the remote clust

### Add the cross-cluster API key to the keystore of the local deployment [ec_add_the_cross_cluster_api_key_to_the_keystore_of_the_local_deployment_2]

The API key created previously will be used by the local deployment to authenticate with the corresponding set of permissions to the remote deployment. For that, you need to add the API key to the local deployment’s keystore.
:::{include} _snippets/apikeys-local-config-intro.md
:::

:::{include} _snippets/apikeys-local-ech-remote-public.md
:::
Expand Down
7 changes: 4 additions & 3 deletions deploy-manage/remote-clusters/ec-remote-cluster-same-ess.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,8 +34,8 @@ If network security policies are applied to the remote cluster, the remote clust

### Prerequisites and limitations [ec_prerequisites_and_limitations]

* The local and remote deployments must be on {{stack}} 8.14 or later.
* Contrary to the certificate security model, the API key security model does not require that both local and remote clusters trust each other.
:::{include} _snippets/apikeys-prerequisites-limitations.md
:::


### Create a cross-cluster API key on the remote deployment [ec_create_a_cross_cluster_api_key_on_the_remote_deployment]
Expand All @@ -45,7 +45,8 @@ If network security policies are applied to the remote cluster, the remote clust

### Add the cross-cluster API key to the local deployment [ec_add_the_cross_cluster_api_key_to_the_local_deployment]

The API key created previously will be used by the local deployment to authenticate with the corresponding set of permissions to the remote deployment. For that, you need to add the API key to the local deployment.
:::{include} _snippets/apikeys-local-config-intro.md
:::

:::{include} _snippets/apikeys-local-ech-remote-public.md
:::
Expand Down
7 changes: 4 additions & 3 deletions deploy-manage/remote-clusters/ec-remote-cluster-self-managed.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,8 +29,8 @@ This section explains how to configure a deployment to connect remotely to self-

### Prerequisites and limitations [ec_prerequisites_and_limitations_4]

* The local and remote deployments must be on {{stack}} 8.14 or later.
* Contrary to the certificate security model, the API key security model does not require that both local and remote clusters trust each other.
:::{include} _snippets/apikeys-prerequisites-limitations.md
:::


### Create a cross-cluster API key on the remote deployment [ec_create_a_cross_cluster_api_key_on_the_remote_deployment_4]
Expand All @@ -40,7 +40,8 @@ This section explains how to configure a deployment to connect remotely to self-

### Configure the local deployment [ec_configure_the_local_deployment_2]

The API key created previously will be used by the local deployment to authenticate with the corresponding set of permissions to the remote deployment. For that, you need to add the API key to the local deployment’s keystore.
:::{include} _snippets/apikeys-local-config-intro.md
:::

The steps to follow depend on whether the Certificate Authority (CA) of the remote environment’s {{es}} HTTPS server, proxy or, load balancing infrastructure is public or private.

Expand Down
6 changes: 4 additions & 2 deletions deploy-manage/remote-clusters/ece-remote-cluster-ece-ess.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,8 @@ If network security filters are applied to the remote cluster on {{ecloud}}, the

### Prerequisites and limitations [ece_prerequisites_and_limitations_3]

* The local and remote deployments must be on {{stack}} 8.14 or later.
:::{include} _snippets/apikeys-prerequisites-limitations.md
:::


### Create a cross-cluster API key on the remote deployment [ece_create_a_cross_cluster_api_key_on_the_remote_deployment_3]
Expand All @@ -45,7 +46,8 @@ If network security filters are applied to the remote cluster on {{ecloud}}, the

### Add the cross-cluster API key to the keystore of the local deployment [ece_add_the_cross_cluster_api_key_to_the_keystore_of_the_local_deployment_2]

The API key created previously will be used by the local deployment to authenticate with the corresponding set of permissions to the remote deployment. For that, you need to add the API key to the local deployment’s keystore.
:::{include} _snippets/apikeys-local-config-intro.md
:::

:::{include} _snippets/apikeys-local-ece-remote-public.md
:::
Expand Down
6 changes: 4 additions & 2 deletions deploy-manage/remote-clusters/ece-remote-cluster-other-ece.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,8 @@ If network security filters are applied to the remote cluster on ECE, the remote

### Prerequisites and limitations [ece_prerequisites_and_limitations_2]

* The local and remote deployments must be on {{stack}} 8.14 or later.
:::{include} _snippets/apikeys-prerequisites-limitations.md
:::

### Create a cross-cluster API key on the remote deployment [ece_create_a_cross_cluster_api_key_on_the_remote_deployment_2]

Expand All @@ -43,7 +44,8 @@ If network security filters are applied to the remote cluster on ECE, the remote

### Configure the local deployment [ece_configure_the_local_deployment]

The API key created previously will be used by the local deployment to authenticate with the corresponding set of permissions to the remote deployment. For that, you need to add the API key to the local deployment’s keystore.
:::{include} _snippets/apikeys-local-config-intro.md
:::

The steps to follow depend on whether the Certificate Authority (CA) of the remote ECE environment’s proxy or load balancing infrastructure is public or private.

Expand Down
6 changes: 4 additions & 2 deletions deploy-manage/remote-clusters/ece-remote-cluster-same-ece.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,8 @@ If network security filters are applied to the remote cluster, the remote cluste

### Prerequisites and limitations [ece_prerequisites_and_limitations]

* The local and remote deployments must be on {{stack}} 8.14 or later.
:::{include} _snippets/apikeys-prerequisites-limitations.md
:::


### Create a cross-cluster API key on the remote deployment [ece_create_a_cross_cluster_api_key_on_the_remote_deployment]
Expand All @@ -44,7 +45,8 @@ If network security filters are applied to the remote cluster, the remote cluste

### Add the cross-cluster API key to the keystore of the local deployment [ece_add_the_cross_cluster_api_key_to_the_keystore_of_the_local_deployment]

The API key created previously will be used by the local deployment to authenticate with the corresponding set of permissions to the remote deployment. For that, you need to add the API key to the local deployment’s keystore.
:::{include} _snippets/apikeys-local-config-intro.md
:::

:::{include} _snippets/apikeys-local-ece-remote-public.md
:::
Expand Down
6 changes: 4 additions & 2 deletions deploy-manage/remote-clusters/ece-remote-cluster-self-managed.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,8 @@ This section explains how to configure a deployment to connect remotely to self-

### Prerequisites and limitations [ece_prerequisites_and_limitations_4]

* The local and remote deployments must be on {{stack}} 8.14 or later.
:::{include} _snippets/apikeys-prerequisites-limitations.md
:::


### Create a cross-cluster API key on the remote deployment [ece_create_a_cross_cluster_api_key_on_the_remote_deployment_4]
Expand All @@ -40,7 +41,8 @@ This section explains how to configure a deployment to connect remotely to self-

### Configure the local deployment [ece_configure_the_local_deployment_2]

The API key created previously will be used by the local deployment to authenticate with the corresponding set of permissions to the remote deployment. For that, you need to add the API key to the local deployment’s keystore.
:::{include} _snippets/apikeys-local-config-intro.md
:::

The steps to follow depend on whether the Certificate Authority (CA) of the remote environment’s {{es}} HTTPS server, proxy or, load balancing infrastructure is public or private.

Expand Down