Skip to content

Commit e426fe1

Browse files
Adding enterprise search comments and links to ECK 2.16 docs (#1062)
ECK 3.0 still supports Enterprise Search for deployments running 8.x versions of Elastic Stack (and maybe even 7.17, although that's irrelevant for the PR). We had removed almost all references to Enterprise Search during the migration and that will look odd considering that some users might still run ECK-managed deployments with Enterprise Search. This PR adds mentions to Enterprise Search in 3 different docs, including links to the 2.16 version of ECK documentation: - [Stack helm chart utilization](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/1062/deploy-manage/deploy/cloud-on-k8s/managing-deployments-using-helm-chart#k8s-install-enterprise-search-elasticsearch-kibana-helm) - [Orchestrating other elastic stack applications](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/1062/deploy-manage/deploy/cloud-on-k8s/orchestrate-other-elastic-applications) - [Network policies examples](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/1062/deploy-manage/security/k8s-network-policies#k8s-network-policies-enterprise-search-isolation) Another approach for this would be to bring back all content related to Enterprise Search from older docs, but maybe it's better this way. @shainaraskas , @bmorelli25 : I'd need to know if the links I'm using for the older documents are correct in terms of destination. And extra question for doc stakeholders: - What should we do with URL mappings of those components? For example https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-enterprise-search.html and all childs have been removed in the new docs system. Should we create redirects or something to point them to the 2.16 version of the docs? or should they all be mapped to the new version of the docs that tells users that Enterprise Search is not supported in 9.x and link to the 2.16 docs? --------- Co-authored-by: shainaraskas <[email protected]>
1 parent ccf7f4f commit e426fe1

File tree

3 files changed

+12
-1
lines changed

3 files changed

+12
-1
lines changed

deploy-manage/deploy/cloud-on-k8s/managing-deployments-using-helm-chart.md

+5-1
Original file line numberDiff line numberDiff line change
@@ -80,7 +80,11 @@ helm install eck-stack-with-apm-server elastic/eck-stack \
8080
--values https://raw.githubusercontent.com/elastic/cloud-on-k8s/2.16/deploy/eck-stack/examples/apm-server/basic.yaml -n elastic-stack
8181
```
8282

83-
## Install individual components of the {{stack}} [k8s-eck-stack-individual-components]
83+
## Enterprise Search server along with {{es}} and {{kib}} [k8s-install-enterprise-search-elasticsearch-kibana-helm]
84+
85+
Enterprise Search is not available in {{stack}} versions 9.0 and later. For an example deployment of {{es}} version 8.x, {{kib}} 8.x, and an 8.x Enterprise Search server using the Helm chart, refer to the [previous ECK documentation](https://www.elastic.co/guide/en/cloud-on-k8s/2.16/k8s-stack-helm-chart.html).
86+
87+
## Install individual components of the {{stack}} [k8s-eck-stack-individual-components]
8488

8589
You can install individual components in one of two ways using the provided Helm Charts.
8690

deploy-manage/deploy/cloud-on-k8s/orchestrate-other-elastic-applications.md

+4
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,10 @@ The following guides provide specific instructions for deploying and configuring
1414
* [Beats](beats.md)
1515
* [{{ls}}](logstash.md)
1616

17+
::::{note}
18+
Enterprise Search is not available in {{stack}} versions 9.0 and later. To deploy or manage Enterprise Search in earlier versions, refer to the [previous ECK documentation](https://www.elastic.co/guide/en/cloud-on-k8s/2.16/k8s-enterprise-search.html).
19+
::::
20+
1721
When orchestrating any of these applications, also consider the following topics:
1822

1923
* [{{stack}} Helm Chart](managing-deployments-using-helm-chart.md)

deploy-manage/security/k8s-network-policies.md

+3
Original file line numberDiff line numberDiff line change
@@ -433,3 +433,6 @@ spec:
433433
common.k8s.elastic.co/type: logstash
434434
```
435435
436+
## Isolating Enterprise Search [k8s-network-policies-enterprise-search-isolation]
437+
438+
Enterprise Search is not available in {{stack}} versions 9.0 and later. For an example of Enterprise Search isolation using network policies in previous {{stack}} versions, refer to the [previous ECK documentation](https://www.elastic.co/guide/en/cloud-on-k8s/2.16/k8s_prerequisites.html#k8s-network-policies-enterprise-search-isolation).

0 commit comments

Comments
 (0)