Deploy and Manage: ECK

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

@@ -10,12 +10,10 @@ mapped_urls:
 
 # Elastic Cloud on Kubernetes [k8s-overview]
 
-::::{important}
-ECK is an Elastic self-managed product offered in two licensing tiers: Basic and Enterprise. For more details refer to [Elastic subscriptions](https://www.elastic.co/subscriptions) and [](/deploy-manage/license/manage-your-license-in-eck.md) documentation.
-::::
-
 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.
 
+## ECK overview
+
 With Elastic Cloud on Kubernetes, you can streamline critical operations, such as:
 
 1. Managing and monitoring multiple clusters
@@ -26,73 +24,70 @@ With Elastic Cloud on Kubernetes, you can streamline critical operations, such a
 
 This section provides everything you need to install, configure, and manage Elastic Stack applications with ECK, including:
 
-- [](./cloud-on-k8s/deploy-an-orchestrator.md): ECK installation methods and configuration details.
-- [](./cloud-on-k8s/manage-deployments.md): Install and configure {{es}} clusters and {{kib}} instances through ECK.
-- [](./cloud-on-k8s/orchestrate-other-elastic-applications.md): Install and configure APM Server, Enterprise Search, Beats, Elastic Agent, Elastic Maps Server, and Logstash on Kubernetes.
+- [](./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/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:
+
+- [Logging and Monitoring](../monitor.md): Configure stack monitoring and logs forwarding with the help of ECK.
+- [Remote Clusters](../remote-clusters.md): Configure remote clusters on ECK.
+- [](../tools.md): Add snapshot repositories to your {{es}} clusters for automatic snapshots.
+- [Security](../security.md): Secure communications, manage HTTP certificates, or add secure settings to your applications.
+- [Users and Roles](../users-roles.md): Configure authentication and authorization mechanisms, built-in users, external providers, and more.
+- [Autoscaling](../autoscaling.md): Learn how to use {{es}} autoscaling on ECK, or use Horizontal Pod Autoscaler functionality for stateless workloads.
+- [Licensing](../license/manage-your-license-in-eck.md): Manage licenses on ECK.
+
+::::{important}
+ECK is an Elastic self-managed product offered in two licensing tiers: Basic and Enterprise. For more details refer to [Elastic subscriptions](https://www.elastic.co/subscriptions) and [](/deploy-manage/license/manage-your-license-in-eck.md) documentation.
+::::
+
 ## Quickstart [eck-quickstart]
 
 If you want to get started quickly, follow these guides to deploy ECK and set up an {{es}} cluster:
 
 * [Install ECK using YAML manifests](./cloud-on-k8s/install-using-yaml-manifest-quickstart.md)
 * [Deploy an {{es}} cluster](./cloud-on-k8s/elasticsearch-deployment-quickstart.md)
 * [Deploy a {{kib}} instance](./cloud-on-k8s/kibana-instance-quickstart.md)
-* [Update your deployment](./cloud-on-k8s/update-deployments.md)
 
-Afterwards, you can find further sample resources [in the project repository](https://github.com/elastic/cloud-on-k8s/tree/2.16/config/samples) or by checking out [our recipes](./cloud-on-k8s/recipes.md).
+Afterwards, you can:
+
+* Learn how to [update your deployment](./cloud-on-k8s/update-deployments.md)
+* Check out [our recipes](./cloud-on-k8s/recipes.md) for multiple use cases
+* Find further sample resources [in the project repository](https://github.com/elastic/cloud-on-k8s/tree/2.16/config/samples)
 
 ## Supported versions [k8s-supported]
 
-ECK is compatible with:
+This section outlines the supported Kubernetes and Elastic Stack versions for ECK. Check the full [Elastic support matrix](https://www.elastic.co/support/matrix#matrix_kubernetes) for more information.
+
+### Kubernetes compatibility
+
+ECK is compatible with the following Kubernetes distributions and related technologies:
 
 * Kubernetes 1.28-1.32
 * OpenShift 4.12-4.17
 * Google Kubernetes Engine (GKE), Azure Kubernetes Service (AKS), and Amazon Elastic Kubernetes Service (EKS)
 * Helm: 3.2.0+
+
+ECK should work with all conformant **installers** listed in these [FAQs](https://github.com/cncf/k8s-conformance/blob/master/faq.md#what-is-a-distribution-hosted-platform-and-an-installer). Distributions include source patches and so may not work as-is with ECK.
+
+### Elastic Stack compatibility
+
+ECK is compatible with the following Elastic Stack applications:
+
 * Elasticsearch, Kibana, APM Server: 6.8+, 7.1+, 8+
 * Enterprise Search: 7.7+, 8+
 * Beats: 7.0+, 8+
 * Elastic Agent: 7.10+ (standalone), 7.14+ (Fleet), 8+
 * Elastic Maps Server: 7.11+, 8+
 * Logstash: 8.7+
 
-ECK should work with all conformant installers listed in these [FAQs](https://github.com/cncf/k8s-conformance/blob/master/faq.md#what-is-a-distribution-hosted-platform-and-an-installer). Distributions include source patches and so may not work as-is with ECK.
-
-Alpha, beta, and stable API versions follow the same [conventions used by Kubernetes](https://kubernetes.io/docs/concepts/overview/kubernetes-api/#api-versioning).
-
 Elastic Stack application images for the OpenShift-certified Elasticsearch (ECK) Operator are only available from version 7.10 and later.
 
-Check the full [Elastic support matrix](https://www.elastic.co/support/matrix#matrix_kubernetes) for more information.
-
-% TBD: discuss if these make sense here
 ## Learn more about ECK [k8s_learn_more_about_eck]
 
 * [Orchestrate Elasticsearch on Kubernetes](https://www.elastic.co/elasticsearch-kubernetes)
 * [ECK post on the Elastic Blog](https://www.elastic.co/blog/introducing-elastic-cloud-on-kubernetes-the-elasticsearch-operator-and-beyond?elektra=products&storm=sub1)
 * [Getting Started With Elastic Cloud on Kubernetes (ECK)](https://www.youtube.com/watch?v=PIJmlYBIFXM)
 * [Running the Elastic Stack on Kubernetes with ECK](https://www.youtube.com/watch?v=Wf6E3vkvEFM)
-
-% TBD: discuss where to put this "ask for help info"
-## Ask for help [k8s-ask-for-help]
-
-If you are an existing Elastic customer with an active support contract, you can create a case in the [Elastic Support Portal](https://support.elastic.co/). Kindly attach an [ECK diagnostic](/troubleshoot/deployments/cloud-on-k8s/run-eck-diagnostics.md) when opening your case.
-
-Alternatively, or if you do not have a support contract, and if you are unable to find a solution to your problem with the information provided in these documents, ask for help:
-
-* [ECK Discuss forums](https://discuss.elastic.co/c/eck) to ask any question
-* [Github issues](https://github.com/elastic/cloud-on-k8s/issues) for bugs and feature requests
-
-% TBD: decide if this should be ommited also.
-% This was a "redirect only" in the excel
-## Advanced topics [k8s-advanced-topics]
-
-* [*Deploy ECK on OpenShift*](/deploy-manage/deploy/cloud-on-k8s/deploy-eck-on-openshift.md)
-* [*Deploy ECK on GKE Autopilot*](/deploy-manage/deploy/cloud-on-k8s/deploy-eck-on-gke-autopilot.md)
-* [*Create custom images*](/deploy-manage/deploy/cloud-on-k8s/create-custom-images.md)
-* [*Service meshes*](/deploy-manage/deploy/cloud-on-k8s/service-meshes.md)
-* [*Traffic Splitting*](/deploy-manage/deploy/cloud-on-k8s/requests-routing-to-elasticsearch-nodes.md)
-* [*Network policies*](/deploy-manage/deploy/cloud-on-k8s/network-policies.md)
-* [*Webhook namespace selectors*](/deploy-manage/deploy/cloud-on-k8s/webhook-namespace-selectors.md)
-* [*Stack Monitoring*](/deploy-manage/monitor/stack-monitoring/eck-stack-monitoring.md)
-* [*Deploy a FIPS compatible version of ECK*](/deploy-manage/deploy/cloud-on-k8s/deploy-fips-compatible-version-of-eck.md)

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

@@ -5,34 +5,14 @@ mapped_urls:
   - https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-accessing-elastic-services.html
   - https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-request-elasticsearch-endpoint.html
   - https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-services.html
-  - https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-security.html
 ---
 
 # Accessing services [k8s-accessing-elastic-services]
 
-% What needs to be done: Refine
-
-% GitHub issue: https://github.com/elastic/docs-projects/issues/357
-
-% Scope notes: Merge the selected docs into one: - First describe how to access Elasticsearch. - Describe the services that ECK creates for ES. - Provide the example and instructions
-
-% Use migrated content from existing pages that map to this page:
-
-% - [ ] ./raw-migrated-files/cloud-on-k8s/cloud-on-k8s/k8s-accessing-elastic-services.md
-% - [ ] ./raw-migrated-files/cloud-on-k8s/cloud-on-k8s/k8s-request-elasticsearch-endpoint.md
-% - [ ] ./raw-migrated-files/cloud-on-k8s/cloud-on-k8s/k8s-services.md
-% - [ ] ./raw-migrated-files/cloud-on-k8s/cloud-on-k8s/k8s-security.md
-
-% Internal links rely on the following IDs being on this page (e.g. as a heading ID, paragraph ID, etc):
-% already present
-$$$k8s-allow-public-access$$$
-% pending
-$$$k8s-setting-up-your-own-certificate$$$
+To provide access to {{es}}, {{kib}}, and, other Elastic Stack applications when applicable, ECK relies on [Kubernetes services](https://kubernetes.io/docs/concepts/services-networking/service/).
 
 All Elastic Stack resources deployed by the ECK operator are secured by default. The operator sets up basic authentication and TLS to encrypt network traffic to, from, and within your Elasticsearch cluster.
 
-To provide access to {{es}} and {{kib}}, ECK creates standard Kubernetes services when orchestrating deployments.
-
 This section explains how to access and customize the Kubernetes services and secrets created by ECK, covering topics such as:
 
 * [Retrieving the `elastic` user password for basic authentication](#k8s-authentication)
@@ -41,15 +21,17 @@ This section explains how to access and customize the Kubernetes services and se
 
 For advanced use cases related to exposing and accessing orchestrated applications, see:
 
-* [](./tls-certificates.md) → Learn how to use the self-signed certificate generated by ECK or configure a custom certificate for the HTTP endpoint.
-* [](./service-meshes.md) → Connect ECK and your managed deployments to service mesh implementations such as `Istio` and `Linkerd`.
-* [](./requests-routing-to-elasticsearch-nodes.md) → Create custom services to expose different node types.
-* [Add Ingress resources through the Helm chart](./managing-deployments-using-helm-chart.md#k8s-eck-stack-ingress).
+* [](/deploy-manage/security/secure-http-communications.md): Configuration options for the HTTP SSL certificates, including integration with certificate management systems such as [cert-manager](https://cert-manager.io/).
+* [](./service-meshes.md): Connect ECK and your managed deployments to service mesh implementations such as [Istio](https://istio.io) and [Linkerd](https://linkerd.io).
+* [](./requests-routing-to-elasticsearch-nodes.md): Create custom services to expose different node types.
+* [Use Ingress to expose {{es}} or {{kib}}](./managing-deployments-using-helm-chart.md#k8s-eck-stack-ingress): Helm based installation also facilitates the creation of Ingress resources.
 
 ## Retrieve the `elastic` user password [k8s-authentication]
 
 To access Elastic resources, the operator manages a default user named `elastic` with the `superuser` role. Its password is stored in a `Secret` named `<name>-elastic-user`.
 
+Run the following command to obtain the password of the `elastic` user:
+
 ```sh
 > kubectl get secret hulk-es-elastic-user -o go-template='{{.data.elastic | base64decode }}'
 42xyz42citsale42xyz42
@@ -59,6 +41,8 @@ To access Elastic resources, the operator manages a default user named `elastic`
 Beware of copying this Secret as-is into a different namespace. Check [Common Problems: Owner References](../../../troubleshoot/deployments/cloud-on-k8s/common-problems.md#k8s-common-problems-owner-refs) for more information.
 ::::
 
+For more information about handling users on ECK deployments refer to [ECK users and roles](/deploy-manage/users-roles/cluster-or-deployment-auth/built-in-users.md).
+
 ## Managing Kubernetes services [k8s-kubernetes-service]
 
 You can access Elastic resources by using native Kubernetes services that are not reachable from the public Internet by default.

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

@@ -168,8 +168,6 @@ Now that you know how to use the APM keystore and customize the server configura
 
 By default the operator manages a private CA and generates a self-signed certificate used to secure the communication between APM agents and the server.
 
-This behavior and the relevant configuration is identical to what is done for Elasticsearch and Kibana. Check [Setting up your own certificate](accessing-services.md#k8s-setting-up-your-own-certificate) for more information on how to use your own certificate to configure the TLS endpoint of the APM Server.
+This behavior and the relevant configuration is identical to what is done for Elasticsearch and Kibana. Check [Setting up your own certificate](/deploy-manage/security/secure-http-communications.md) for more information on how to use your own certificate to configure the TLS endpoint of the APM Server.
 
 For more details on how to configure the APM agents to work with custom certificates, check the [APM agents documentation](https://www.elastic.co/guide/en/apm/agent/index.html).
-
-

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

@@ -223,7 +223,7 @@ To deploy {{agent}} in clusters with the Pod Security Policy admission controlle
 
 ## Customize {{fleet-server}} Service [k8s-elastic-agent-fleet-configuration-customize-fleet-server-service]
 
-By default, ECK creates a Service for {{fleet-server}} that {{agents}} can connect through. You can customize it using the `http` configuration element. Check more information on how to [make changes](accessing-services.md) to the Service and [customize](tls-certificates.md) the TLS configuration.
+By default, ECK creates a Service for {{fleet-server}} that {{agents}} can connect through. You can customize it using the `http` configuration element. Check more information on how to [make changes](accessing-services.md) to the Service and [customize](/deploy-manage/security/secure-http-communications.md) the TLS configuration.
 
 
 ## Control {{fleet}} policy selection [k8s-elastic-agent-control-fleet-policy-selection]

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

@@ -6,43 +6,30 @@ mapped_pages:
   - https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-update-deployment.html
 ---
 
-% the security link needs to be refined to point to the eck related section around security
-% same for upgrade link
-
 # Configure deployments [k8s-orchestrating-elastic-stack-applications]
 
 This section provides details around {{kib}} and {{es}} configuration when running on ECK. For general information about how ECK applies configuration changes and the syntax to use in the YAML manifests, refer to [](./update-deployments.md).
 
-* [**{{es}} configuration**](elasticsearch-configuration.md) → Review configuration possibilities to tune your {{es}} cluster running on ECK, learn how [nodes orchestration](./nodes-orchestration.md) work, [storage recommendations](./storage-recommendations.md), and more.
-
-  * [](./requests-routing-to-elasticsearch-nodes.md) → Control the nodes receiving incoming traffic when using multiple `nodeSets` with different [node roles](https://www.elastic.co/guide/en/elasticsearch/reference/current/node-roles-overview.html).
+* [**{{es}} configuration**](elasticsearch-configuration.md): Review configuration possibilities to tune your {{es}} cluster running on ECK, learn how [nodes orchestration](./nodes-orchestration.md) work, [storage recommendations](./storage-recommendations.md), and more.
 
-* [**{{kib}} configuration**](kibana-configuration.md) → Learn how to connect {{kib}} to an {{es}} cluster, apply advanced configuration settings, and tune the HTTP configuration.
+* [**{{kib}} configuration**](kibana-configuration.md): Learn how to connect {{kib}} to an {{es}} cluster, apply advanced configuration settings, and tune the HTTP configuration.
 
 Additionally, the following topics apply to both {{es}} and {{kib}}, and in some cases, to other applications supported by ECK:
 
-* [**Access services**](accessing-services.md) → Learn how to access to the orchestrated clusters and how to adapt the Kubernetes services to your needs.
-
-* [**TLS certificates**](./tls-certificates.md) → Use your own SSL/TLS certificates for the HTTP endpoint of {{es}} or {{kib}}.
-
-* [**Secure the Elastic Stack**](../../security.md) → Manage users and roles, authentication realms, and more.
+* [**Access services**](accessing-services.md): Learn how to access to the orchestrated clusters and how to adapt the Kubernetes services to your needs.
 
-* [**Recipes**](recipes.md) → Advanced use cases examples available in our GitHub repository. 
+* [**Customize Pods**](customize-pods.md): Learn how to adapt the `podTemplate` field to your needs.
 
-* [**Customize Pods**](customize-pods.md) → Learn how to adapt the `podTemplate` field to your needs.
+* [**Manage compute resources**](manage-compute-resources.md): Important considerations around CPU and memory `requests` and `limits` when running production workloads.
 
-* [**Manage compute resources**](manage-compute-resources.md) → Important considerations around CPU and memory when running production workloads.
+* [**Recipes**](recipes.md): Advanced use cases examples available in our GitHub repository. 
 
-* [**Autoscaling stateless applications**](../../autoscaling/autoscaling-stateless-applications-on-eck.md) → Use [Horizontal Pod Autoscaler](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/) for {{kib}} or other stateless applications.
-
-* [**Connect to external Elastic resources**](connect-to-external-elastic-resources.md) → Use `secrets` with custom settings for `elasticsearchRef` and `kibanaRef` parameters.
+* [**Connect to external Elastic resources**](connect-to-external-elastic-resources.md): Use custom `secrets` for the `elasticsearchRef` and `kibanaRef` parameters.
 
 ECK also facilitates configuration and operation activities with advanced features, such as:
 
-* [**Elastic Stack configuration policies**](elastic-stack-configuration-policies.md) → Organize your {{es}} and {{kib}} configuration settings through `StackConfigPolicy` resources that can be referenced within your deployments.
-
-* [**Stack monitoring**](https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-stack-monitoring.html) → Monitor your deployments smoothly with the help of ECK.
-
-* [**Remote clusters**](/deploy-manage/remote-clusters/eck-remote-clusters.md) → Configure {{es}} remote clusters functionality for Cross Cluster Search (CCS) and Cross Cluster Replication.
+* [**Elastic Stack configuration policies**](elastic-stack-configuration-policies.md): Organize your {{es}} and {{kib}} configuration settings through `StackConfigPolicy` resources that can be referenced within your deployments. This helps to keep your manifests simplified.
 
-* [**Upgrade the Elastic Stack version**](../../upgrade/deployment-or-cluster.md) → Upgrade orchestrated applications on ECK.
+::::{important}
+Explore the [Security](/deploy-manage/security.md) section for configuration options such as user and role management, configuring security realms, securing HTTP communications, and more.
+::::