removed references to enterprise search

eedugon · eedugon · commit 9315da5282fe · 2025-02-18T17:14:34.000+01:00
diff --git a/deploy-manage/deploy/cloud-on-k8s.md b/deploy-manage/deploy/cloud-on-k8s.md
@@ -10,7 +10,7 @@ mapped_urls:
 
 # Elastic Cloud on Kubernetes [k8s-overview]
 
-Built on the Kubernetes Operator pattern, {{eck}} (ECK) extends the basic Kubernetes orchestration capabilities to support the setup and management of Elasticsearch, Kibana, APM Server, Enterprise Search, Beats, Elastic Agent, Elastic Maps Server, and Logstash on Kubernetes.
+Built on the Kubernetes Operator pattern, {{eck}} (ECK) extends the basic Kubernetes orchestration capabilities to support the setup and management of Elasticsearch, Kibana, APM Server, Beats, Elastic Agent, Elastic Maps Server, and Logstash on Kubernetes.
 
 ## ECK overview
 
@@ -26,7 +26,7 @@ This section provides everything you need to install, configure, and manage Elas
 
 - [](./cloud-on-k8s/deploy-an-orchestrator.md): ECK installation methods and configuration options. Deploy ECK on managed Kubernetes platforms like GKE, AKS, and EKS, on self-managed Kubernetes clusters, on OpenShift, and even in air-gapped environments.
 - [](./cloud-on-k8s/manage-deployments.md): Handle {{es}} clusters and {{kib}} instances through ECK.
-- [](./cloud-on-k8s/orchestrate-other-elastic-applications.md): Run APM Server, Enterprise Search, Beats, Elastic Agent, Elastic Maps Server, and Logstash on Kubernetes.
+- [](./cloud-on-k8s/orchestrate-other-elastic-applications.md): Run APM Server, Beats, Elastic Agent, Elastic Maps Server, and Logstash on Kubernetes.
 - [](./cloud-on-k8s/tools-apis.md): A collection of tools and APIs available in ECK based environments.
 
 Other sections of the documentation include the following important topics around ECK:
diff --git a/deploy-manage/deploy/cloud-on-k8s/air-gapped-install.md b/deploy-manage/deploy/cloud-on-k8s/air-gapped-install.md
@@ -88,7 +88,7 @@ Once the ECK operator image is copied internally, replace the original image nam
 
 ## Override the default container registry [k8s-container-registry-override]
 
-When creating custom resources (Elasticsearch, Kibana, APM Server, Enterprise Search, Beats, Elastic Agent, Elastic Maps Server, and Logstash), the operator defaults to using container images pulled from the `docker.elastic.co` registry. If you are in an environment where external network access is restricted, you can configure the operator to use a different default container registry by starting the operator with the `--container-registry` command-line flag. Check [*Configure ECK*](../../../deploy-manage/deploy/cloud-on-k8s/configure-eck.md) for more information on how to configure the operator using command-line flags and environment variables.
+When creating custom resources (Elasticsearch, Kibana, APM Server, Beats, Elastic Agent, Elastic Maps Server, and Logstash), the operator defaults to using container images pulled from the `docker.elastic.co` registry. If you are in an environment where external network access is restricted, you can configure the operator to use a different default container registry by starting the operator with the `--container-registry` command-line flag. Check [*Configure ECK*](../../../deploy-manage/deploy/cloud-on-k8s/configure-eck.md) for more information on how to configure the operator using command-line flags and environment variables.
 
 The operator expects container images to be located at specific repositories in the default container registry. Make sure that your container images are stored in the right repositories and are tagged correctly with the Stack version number. For example, if your private registry is `my.registry` and you wish to deploy components from Stack version 8.16.1, the following image names should exist:
 
diff --git a/deploy-manage/deploy/cloud-on-k8s/configure-validating-webhook.md b/deploy-manage/deploy/cloud-on-k8s/configure-validating-webhook.md
@@ -26,7 +26,7 @@ Validating webhooks are defined using a `ValidatingWebhookConfiguration` object
 
 When using the default `operator.yaml` manifest, ECK is installed with a `ValidatingWebhookConfiguration` configured as follows:
 
-* Validate all known Elastic custom resources (Elasticsearch, Kibana, APM Server, Enterprise Search, Beats, Elastic Agent, Elastic Maps Server, and Logstash) on create and update.
+* Validate all known Elastic custom resources (Elasticsearch, Kibana, APM Server, Beats, Elastic Agent, Elastic Maps Server, and Logstash) on create and update.
 * The operator itself is the webhook server — which is exposed through a service named `elastic-webhook-server` in the `elastic-system` namespace.
 * The operator generates a certificate for the webhook and stores it in a secret named `elastic-webhook-server-cert` in the `elastic-system` namespace. This certificate is automatically rotated by the operator when it is due to expire.
 
diff --git a/deploy-manage/deploy/cloud-on-k8s/deploy-eck-on-openshift.md b/deploy-manage/deploy/cloud-on-k8s/deploy-eck-on-openshift.md
@@ -17,10 +17,6 @@ This section shows how to run ECK on OpenShift.
 * [Grant privileged permissions to Beats](k8s-openshift-beats.md)
 * [Grant host access permission to Elastic Agent](k8s-openshift-agent.md)
 
-::::{warning} 
-Some Docker images are incompatible with the `restricted` SCC. This is the case for the **APM Server before 7.9** and for **Enterprise Search 7.9 and 7.10**. You can use this [workaround](k8s-openshift-anyuid-workaround.md) to run those images with the `anyuid` SCC.
-::::
-
 ## Before you begin [k8s-openshift-before-you-begin] 
 
 1. To run the instructions on this page, you must be a `system:admin` user or a user with the privileges to create Projects, CRDs, and RBAC resources at the cluster level.
diff --git a/deploy-manage/deploy/cloud-on-k8s/install-using-yaml-manifest-quickstart.md b/deploy-manage/deploy/cloud-on-k8s/install-using-yaml-manifest-quickstart.md
@@ -15,7 +15,7 @@ To learn about other installation methods, refer to [](/deploy-manage/deploy/clo
 
 During the installation, the following components are installed or updated:
 
-* `CustomResourceDefinition` objects for all supported resource types (Elasticsearch, Kibana, APM Server, Enterprise Search, Beats, Elastic Agent, Elastic Maps Server, and Logstash).
+* `CustomResourceDefinition` objects for all supported resource types (Elasticsearch, Kibana, APM Server, Beats, Elastic Agent, Elastic Maps Server, and Logstash).
 * `Namespace` named `elastic-system` to hold all operator resources.
 * `ServiceAccount`, `ClusterRole` and `ClusterRoleBinding` to allow the operator to manage resources throughout the cluster.
 * `ValidatingWebhookConfiguration` to validate Elastic custom resources on admission.
diff --git a/deploy-manage/deploy/cloud-on-k8s/install.md b/deploy-manage/deploy/cloud-on-k8s/install.md
@@ -8,7 +8,7 @@ mapped_urls:
 
 # Install ECK [k8s-installing-eck]
 
-Elastic Cloud on Kubernetes (ECK) is a [Kubernetes operator](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) that helps you deploy and manage Elastic applications on Kubernetes, including Elasticsearch, Kibana, APM Server, Enterprise Search, Beats, Elastic Agent, Elastic Maps Server, and Logstash.
+Elastic Cloud on Kubernetes (ECK) is a [Kubernetes operator](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) that helps you deploy and manage Elastic applications on Kubernetes, including Elasticsearch, Kibana, APM Server, Beats, Elastic Agent, Elastic Maps Server, and Logstash.
 
 ECK relies on a set of [Custom Resource Definitions (CRDs)](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/#customresourcedefinitions) to define how applications are deployed. CRDs are global resources, shared across the entire Kubernetes cluster, so installing them requires [specific permissions](../../../deploy-manage/deploy/cloud-on-k8s/required-rbac-permissions.md#k8s-eck-permissions-installing-crds).
 
@@ -21,7 +21,7 @@ You can install multiple instances of ECK in the same Kubernetes cluster, but on
 ::::
 
 ::::{warning}
-Deleting CRDs will trigger deletion of all custom resources (Elasticsearch, Kibana, APM Server, Enterprise Search, Beats, Elastic Agent, Elastic Maps Server, and Logstash) in all namespaces of the cluster, regardless of whether they are managed by a single operator or multiple operators.
+Deleting CRDs will trigger deletion of all custom resources (Elasticsearch, Kibana, APM Server, Beats, Elastic Agent, Elastic Maps Server, and Logstash) in all namespaces of the cluster, regardless of whether they are managed by a single operator or multiple operators.
 ::::
 
 For a list of supported Kubernetes versions refer to [](../cloud-on-k8s.md#k8s-supported)
diff --git a/deploy-manage/deploy/cloud-on-k8s/k8s-openshift-anyuid-workaround.md b/deploy-manage/deploy/cloud-on-k8s/k8s-openshift-anyuid-workaround.md
@@ -7,7 +7,7 @@ mapped_pages:
 
 # Deploy Docker images with anyuid SCC [k8s-openshift-anyuid-workaround]
 
-Starting with version 7.9, it is possible to run the APM Server with the `restricted` SCC. For APM versions older than 7.9 and Enterprise Search version 7.9, you can use this workaround which allows the Pod to run with the default `uid 1000` by assigning it to the `anyuid` SCC:
+Starting with version 7.9, it is possible to run the APM Server with the `restricted` SCC. For APM versions older than 7.9, you can use this workaround which allows the Pod to run with the default `uid 1000` by assigning it to the `anyuid` SCC:
 
 1. Create a service account to run the APM Server:
 
@@ -71,7 +71,6 @@ Starting with version 7.9, it is possible to run the APM Server with the `restri
     kibana-sample-kb-97c6b6b8d-lqfd2 scc:restricted
     ```
 
-
 :::{important}
 Enterprise Search is not available in versions 9.0+.
 :::
diff --git a/deploy-manage/deploy/cloud-on-k8s/manage-compute-resources.md b/deploy-manage/deploy/cloud-on-k8s/manage-compute-resources.md
@@ -104,7 +104,7 @@ A [known Kubernetes issue](https://github.com/kubernetes/kubernetes/issues/51135
 
 
 
-### Set compute resources for Kibana, Enterprise Search, Elastic Maps Server, APM Server and Logstash [k8s-compute-resources-kibana-and-apm]
+### Set compute resources for Kibana, Elastic Maps Server, APM Server and Logstash [k8s-compute-resources-kibana-and-apm]
 
 ```yaml
 apiVersion: kibana.k8s.elastic.co/v1
@@ -287,7 +287,6 @@ If `resources` is not defined in the specification of an object, then the operat
 | Beat | `300Mi` | `300Mi` |
 | Elastic Agent | `400Mi` | `400Mi` |
 | Elastic Maps Server | `200Mi` | `200Mi` |
-| Enterprise Search | `4Gi` | `4Gi` |
 | Logstash | `2Gi` | `2Gi` |
 
 If the Kubernetes cluster is configured with [LimitRanges](https://kubernetes.io/docs/tasks/administer-cluster/manage-resources/memory-default-namespace/) that enforce a minimum memory constraint, they could interfere with the operator defaults and cause object creation to fail.
diff --git a/deploy-manage/deploy/cloud-on-k8s/manage-deployments.md b/deploy-manage/deploy/cloud-on-k8s/manage-deployments.md
@@ -7,7 +7,7 @@ applies:
 This section provides detailed guidance on deploying, configuring, and managing Elasticsearch and Kibana within ECK. A **deployment** refers to an {{es}} cluster, optionally with one or more {{kib}} instances connected to it.
 
 ::::{tip}
-This content focuses on Elasticsearch and Kibana deployments. To orchestrate other Elastic Stack applications such as APM Server, Enterprise Search, Beats, Elastic Agent, Elastic Maps Server, and Logstash, refer to the [Orchestrating other Elastic Stack applications](./orchestrate-other-elastic-applications.md).
+This content focuses on Elasticsearch and Kibana deployments. To orchestrate other Elastic Stack applications such as APM Server, Beats, Elastic Agent, Elastic Maps Server, and Logstash, refer to the [Orchestrating other Elastic Stack applications](./orchestrate-other-elastic-applications.md).
 ::::
 
 ## What You'll Learn
diff --git a/deploy-manage/deploy/cloud-on-k8s/network-policies.md b/deploy-manage/deploy/cloud-on-k8s/network-policies.md
@@ -274,53 +274,6 @@ spec:
       common.k8s.elastic.co/type: apm-server
 ```
 
-
-## Isolating Enterprise Search [k8s-network-policies-enterprise-search-isolation] 
-
-|     |     |
-| --- | --- |
-| Egress (outgoing) | * TCP port 9200 to {{es}} nodes in the namespace.<br>* UDP port 53 for DNS lookup.<br> |
-| Ingress (incoming) | * TCP port 3002 from other pods in the namespace.<br> |
-
-```yaml
-apiVersion: networking.k8s.io/v1
-kind: NetworkPolicy
-metadata:
-  name: eck-enterprise-search
-  namespace: team-a
-spec:
-  egress:
-  - ports:
-    - port: 9200
-      protocol: TCP
-    to:
-    - namespaceSelector:
-        matchLabels:
-          eck.k8s.elastic.co/tenant: team-a
-      podSelector:
-        matchLabels:
-          common.k8s.elastic.co/type: elasticsearch
-  - ports:
-    - port: 53
-      protocol: UDP
-  ingress:
-  - from:
-    - namespaceSelector:
-        matchLabels:
-          eck.k8s.elastic.co/tenant: team-a
-    # [Optional] Allow ingress controller pods from the ingress-nginx namespace.
-    #- namespaceSelector:
-    #    matchLabels:
-    #      name: ingress-nginx
-    ports:
-    - port: 3002
-      protocol: TCP
-  podSelector:
-    matchLabels:
-      common.k8s.elastic.co/type: enterprise-search
-```
-
-
 ## Isolating Beats [k8s-network-policies-beats-isolation] 
 
 ::::{note} 
diff --git a/deploy-manage/deploy/cloud-on-k8s/orchestrate-other-elastic-applications.md b/deploy-manage/deploy/cloud-on-k8s/orchestrate-other-elastic-applications.md
@@ -3,15 +3,14 @@
 This section explains how to deploy and configure various Elastic Stack applications within Elastic Cloud on Kubernetes (ECK).
 
 ::::{tip}
-This content applies to APM Server, Enterprise Search, Beats, Elastic Agent, Elastic Maps Server, and Logstash applications. To orchestrate an {{es}} cluster or {{kib}}, refer to [](./manage-deployments.md).
+This content applies to APM Server, Beats, Elastic Agent, Elastic Maps Server, and Logstash applications. To orchestrate an {{es}} cluster or {{kib}}, refer to [](./manage-deployments.md).
 ::::
 
 The following guides provide specific instructions for deploying and configuring each application on ECK:
 * [APM Server](apm-server.md)
 * [Standalone Elastic Agent](standalone-elastic-agent.md)
 * [{{fleet}}-managed {{agent}}](fleet-managed-elastic-agent.md)
 * [Elastic Maps Server](elastic-maps-server.md)
-* [Enterprise Search](enterprise-search.md)
 * [Beats](beats.md)
 * [{{ls}}](logstash.md)
 
