Merge branch 'main' into add-failure-store

Author: mdbirnstiehl

deploy-manage/deploy/cloud-on-k8s/configuration-examples-beats.md

@@ -19,7 +19,7 @@ The examples in this section are purely descriptive and should not be considered
 
 ## Metricbeat for Kubernetes monitoring [k8s_metricbeat_for_kubernetes_monitoring]
 
-```sh
+```sh subs=true
 kubectl apply -f https://raw.githubusercontent.com/elastic/cloud-on-k8s/{{eck_release_branch}}/config/recipes/beats/metricbeat_hosts.yaml
 ```
 
@@ -31,7 +31,7 @@ Deploys Metricbeat as a DaemonSet that monitors the usage of the following resou
 
 ## Filebeat with autodiscover [k8s_filebeat_with_autodiscover]
 
-```sh
+```sh subs=true
 kubectl apply -f https://raw.githubusercontent.com/elastic/cloud-on-k8s/{{eck_release_branch}}/config/recipes/beats/filebeat_autodiscover.yaml
 ```
 
@@ -40,7 +40,7 @@ Deploys Filebeat as a DaemonSet with the autodiscover feature enabled. It collec
 
 ## Filebeat with autodiscover for metadata [k8s_filebeat_with_autodiscover_for_metadata]
 
-```sh
+```sh subs=true
 kubectl apply -f https://raw.githubusercontent.com/elastic/cloud-on-k8s/{{eck_release_branch}}/config/recipes/beats/filebeat_autodiscover_by_metadata.yaml
 ```
 
@@ -52,7 +52,7 @@ Deploys Filebeat as a DaemonSet with the autodiscover feature enabled. Logs from
 
 ## Filebeat without autodiscover [k8s_filebeat_without_autodiscover]
 
-```sh
+```sh subs=true
 kubectl apply -f https://raw.githubusercontent.com/elastic/cloud-on-k8s/{{eck_release_branch}}/config/recipes/beats/filebeat_no_autodiscover.yaml
 ```
 
@@ -61,7 +61,7 @@ Deploys Filebeat as a DaemonSet with the autodiscover feature disabled. Uses the
 
 ## {{es}} and {{kib}} Stack Monitoring [k8s_elasticsearch_and_kibana_stack_monitoring]
 
-```sh
+```sh subs=true
 kubectl apply -f https://raw.githubusercontent.com/elastic/cloud-on-k8s/{{eck_release_branch}}/config/recipes/beats/stack_monitoring.yaml
 ```
 
@@ -75,7 +75,7 @@ In this example, TLS verification is disabled when Metricbeat communicates with
 
 ## Heartbeat monitoring {{es}} and {{kib}} health [k8s_heartbeat_monitoring_elasticsearch_and_kibana_health]
 
-```sh
+```sh subs=true
 kubectl apply -f https://raw.githubusercontent.com/elastic/cloud-on-k8s/{{eck_release_branch}}/config/recipes/beats/heartbeat_es_kb_health.yaml
 ```
 
@@ -84,7 +84,7 @@ Deploys Heartbeat as a single Pod deployment that monitors the health of {{es}}
 
 ## Auditbeat [k8s_auditbeat]
 
-```sh
+```sh subs=true
 kubectl apply -f https://raw.githubusercontent.com/elastic/cloud-on-k8s/{{eck_release_branch}}/config/recipes/beats/auditbeat_hosts.yaml
 ```
 
@@ -93,7 +93,7 @@ Deploys Auditbeat as a DaemonSet that checks file integrity and audits file oper
 
 ## Packetbeat monitoring DNS and HTTP traffic [k8s_packetbeat_monitoring_dns_and_http_traffic]
 
-```sh
+```sh subs=true
 kubectl apply -f https://raw.githubusercontent.com/elastic/cloud-on-k8s/{{eck_release_branch}}/config/recipes/beats/packetbeat_dns_http.yaml
 ```
 
@@ -102,7 +102,7 @@ Deploys Packetbeat as a DaemonSet that monitors DNS on port `53` and HTTP(S) tra
 
 ## OpenShift monitoring [k8s_openshift_monitoring]
 
-```sh
+```sh subs=true
 kubectl apply -f https://raw.githubusercontent.com/elastic/cloud-on-k8s/{{eck_release_branch}}/config/recipes/beats/openshift_monitoring.yaml
 ```
 

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

@@ -19,7 +19,7 @@ The examples in this section are for illustration purposes only and should not b
 
 ## System and {{k8s}} {{integrations}} [k8s_system_and_k8s_integrations]
 
-```sh
+```sh subs=true
 kubectl apply -f https://raw.githubusercontent.com/elastic/cloud-on-k8s/{{eck_release_branch}}/config/recipes/elastic-agent/fleet-kubernetes-integration.yaml
 ```
 
@@ -28,7 +28,7 @@ Deploys {{agent}} as a DaemonSet in {{fleet}} mode with System and {{k8s}} {{int
 
 ## System and {{k8s}} {{integrations}} running as non-root [k8s_system_and_k8s_integrations_running_as_non_root]
 
-```sh
+```sh subs=true
 kubectl apply -f https://raw.githubusercontent.com/elastic/cloud-on-k8s/{{eck_release_branch}}/config/recipes/elastic-agent/fleet-kubernetes-integration-nonroot.yaml
 ```
 
@@ -42,7 +42,7 @@ The DaemonSet itself must run as root to set up permissions and ECK >= 2.10.0 is
 
 ## Custom logs integration with autodiscover [k8s_custom_logs_integration_with_autodiscover]
 
-```sh
+```sh subs=true
 kubectl apply -f https://raw.githubusercontent.com/elastic/cloud-on-k8s/{{eck_release_branch}}/config/recipes/elastic-agent/fleet-custom-logs-integration.yaml
 ```
 
@@ -51,7 +51,7 @@ Deploys {{agent}} as a DaemonSet in {{fleet}} mode with Custom Logs integration
 
 ## APM integration [k8s_apm_integration]
 
-```sh
+```sh subs=true
 kubectl apply -f https://raw.githubusercontent.com/elastic/cloud-on-k8s/{{eck_release_branch}}/config/recipes/elastic-agent/fleet-apm-integration.yaml
 ```
 
@@ -60,7 +60,7 @@ Deploys single instance {{agent}} Deployment in {{fleet}} mode with APM integrat
 
 ## Synthetic monitoring [k8s_synthetic_monitoring]
 
-```sh
+```sh subs=true
 kubectl apply -f https://raw.githubusercontent.com/elastic/cloud-on-k8s/{{eck_release_branch}}/config/recipes/elastic-agent/synthetic-monitoring.yaml
 ```
 

deploy-manage/deploy/cloud-on-k8s/configuration-examples-logstash.md

@@ -19,7 +19,7 @@ The examples in this section are for illustration purposes only. They should not
 
 ## Single pipeline defined in CRD [k8s-logstash-configuration-single-pipeline-crd]
 
-```sh
+```sh subs=true
 kubectl apply -f https://raw.githubusercontent.com/elastic/cloud-on-k8s/{{eck_release_branch}}/config/recipes/logstash/logstash-eck.yaml
 ```
 
@@ -28,7 +28,7 @@ Deploys Logstash with a single pipeline defined in the CRD
 
 ## Single Pipeline defined in Secret [k8s-logstash-configuration-single-pipeline-secret]
 
-```sh
+```sh subs=true
 kubectl apply -f https://raw.githubusercontent.com/elastic/cloud-on-k8s/{{eck_release_branch}}/config/recipes/logstash/logstash-pipeline-as-secret.yaml
 ```
 
@@ -37,7 +37,7 @@ Deploys Logstash with a single pipeline defined in a secret, referenced by a `pi
 
 ## Pipeline configuration in mounted volume [k8s-logstash-configuration-pipeline-volume]
 
-```sh
+```sh subs=true
 kubectl apply -f https://raw.githubusercontent.com/elastic/cloud-on-k8s/{{eck_release_branch}}/config/recipes/logstash/logstash-pipeline-as-volume.yaml
 ```
 
@@ -46,7 +46,7 @@ Deploys Logstash with a single pipeline defined in a secret, mounted as a volume
 
 ## Writing to a custom {{es}} index [k8s-logstash-configuration-custom-index]
 
-```sh
+```sh subs=true
 kubectl apply -f https://raw.githubusercontent.com/elastic/cloud-on-k8s/{{eck_release_branch}}/config/recipes/logstash/logstash-es-role.yaml
 ```
 
@@ -55,7 +55,7 @@ Deploys Logstash and {{es}}, and creates an updated version of the `eck_logstash
 
 ## Creating persistent volumes for PQ and DLQ [k8s-logstash-configuration-pq-dlq]
 
-```sh
+```sh subs=true
 kubectl apply -f https://raw.githubusercontent.com/elastic/cloud-on-k8s/{{eck_release_branch}}/config/recipes/logstash/logstash-volumes.yaml
 ```
 
@@ -67,7 +67,7 @@ Deploys Logstash, Beats and {{es}}. Logstash is configured with two pipelines:
 
 ## {{es}} and {{kib}} Stack Monitoring [k8s-logstash-configuration-stack-monitoring]
 
-```sh
+```sh subs=true
 kubectl apply -f https://raw.githubusercontent.com/elastic/cloud-on-k8s/{{eck_release_branch}}/config/recipes/logstash/logstash-monitored.yaml
 ```
 
@@ -76,7 +76,7 @@ Deploys an {{es}} and {{kib}} monitoring cluster, and a Logstash that will send
 
 ## Multiple pipelines/multiple {{es}} clusters [k8s-logstash-configuration-multiple-pipelines]
 
-```sh
+```sh subs=true
 kubectl apply -f https://raw.githubusercontent.com/elastic/cloud-on-k8s/{{eck_release_branch}}/config/recipes/logstash/logstash-multi.yaml
 ```
 

deploy-manage/deploy/cloud-on-k8s/configuration-examples-standalone.md

@@ -19,7 +19,7 @@ The examples in this section are for illustration purposes only and should not b
 
 ## System integration [k8s_system_integration]
 
-```sh
+```sh subs=true
 kubectl apply -f https://raw.githubusercontent.com/elastic/cloud-on-k8s/{{eck_release_branch}}/config/recipes/elastic-agent/system-integration.yaml
 ```
 
@@ -28,7 +28,7 @@ Deploys Elastic Agent as a DaemonSet in standalone mode with system integration
 
 ## Kubernetes integration [k8s_kubernetes_integration]
 
-```sh
+```sh subs=true
 kubectl apply -f https://raw.githubusercontent.com/elastic/cloud-on-k8s/{{eck_release_branch}}/config/recipes/elastic-agent/kubernetes-integration.yaml
 ```
 
@@ -37,7 +37,7 @@ Deploys Elastic Agent as a DaemonSet in standalone mode with Kubernetes integrat
 
 ## Multiple {{es}} clusters output [k8s_multiple_elasticsearch_clusters_output]
 
-```sh
+```sh subs=true
 kubectl apply -f https://raw.githubusercontent.com/elastic/cloud-on-k8s/{{eck_release_branch}}/config/recipes/elastic-agent/multi-output.yaml
 ```
 

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

@@ -45,7 +45,7 @@ You can find example Helm values files for deploying and managing more advanced
 
 To use one or more of these example configurations, use the `--values` Helm option, as seen in the following section.
 
-```sh
+```sh subs=true
 # Install an eck-managed Elasticsearch and Kibana using the Elasticsearch node roles example with hot, warm, and cold data tiers, and the Kibana example customizing the http service.
 helm install es-quickstart elastic/eck-stack -n elastic-stack --create-namespace \
     --values https://raw.githubusercontent.com/elastic/cloud-on-k8s/{{eck_release_branch}}/deploy/eck-stack/examples/elasticsearch/hot-warm-cold.yaml \
@@ -56,7 +56,7 @@ helm install es-quickstart elastic/eck-stack -n elastic-stack --create-namespace
 
 The following section builds upon the previous section, and allows installing Fleet Server, and Fleet-managed Elastic Agents along with {{es}} and {{kib}}.
 
-```sh
+```sh subs=true
 # Install an eck-managed Elasticsearch, Kibana, Fleet Server, and managed Elastic Agents using custom values.
 helm install eck-stack-with-fleet elastic/eck-stack \
     --values https://raw.githubusercontent.com/elastic/cloud-on-k8s/{{eck_release_branch}}/deploy/eck-stack/examples/agent/fleet-agents.yaml -n elastic-stack
@@ -66,7 +66,7 @@ helm install eck-stack-with-fleet elastic/eck-stack \
 
 The following section builds upon the previous sections, and allows installing Logstash along with {{es}}, {{kib}} and Beats.
 
-```sh
+```sh subs=true
 # Install an eck-managed Elasticsearch, Kibana, Beats and Logstash using custom values.
 helm install eck-stack-with-logstash elastic/eck-stack \
     --values https://raw.githubusercontent.com/elastic/cloud-on-k8s/{{eck_release_branch}}/deploy/eck-stack/examples/logstash/basic-eck.yaml -n elastic-stack
@@ -76,7 +76,7 @@ helm install eck-stack-with-logstash elastic/eck-stack \
 
 The following section builds upon the previous sections, and allows installing a standalone Elastic APM Server along with {{es}} and {{kib}}.
 
-```sh
+```sh subs=true
 # Install an eck-managed Elasticsearch, Kibana, and standalone APM Server using custom values.
 helm install eck-stack-with-apm-server elastic/eck-stack \
     --values https://raw.githubusercontent.com/elastic/cloud-on-k8s/{{eck_release_branch}}/deploy/eck-stack/examples/apm-server/basic.yaml -n elastic-stack

deploy-manage/upgrade/deployment-or-cluster/upgrade-on-ech.md

@@ -16,12 +16,22 @@ products:
 
 Once you are [prepared to upgrade](/deploy-manage/upgrade/prepare-to-upgrade.md), a single click in the {{ecloud}} console can upgrade a deployment to a newer version, add more processing capacity, change plugins, and enable or disable high availability, all at the same time. During the upgrade process, {{es}}, {{kib}}, Elastic APM, and all of your deployment components are upgraded simultaneously.
 
-You can perform minor version upgrades, upgrades from 8.18 to 9.0.0, and cluster configuration changes with no downtime. {{ecloud}} only supports upgrades to released versions. Release candidate builds and master snapshots are not supported.
+{{ecloud}} only supports upgrades to released versions. Release candidate builds and master snapshots are not supported.
 
 ::::{important}
 Although it’s simple to upgrade an {{ecloud}} deployment, the new version might include breaking changes that affect your application. Ensure you review breaking changes and deprecation logs, make any necessary changes, and test against the new version before upgrading your production deployment.
 ::::
 
+## Availability during upgrades
+
+For deployments with nodes in more than one availability zone, you can perform minor version upgrades, upgrades from 8.18 to 9.0.0, and cluster configuration changes with no downtime. Deployments with nodes in only one zone might experience downtime during these operations.
+
+When {{kib}} instances are upgraded, all instances are shut down simultaneously, making {{kib}} temporarily inaccessible, even if it's deployed across multiple zones.
+
+If your indices are not highly available (configured with at least one replica), or if certain components of your deployment run in only one zone, you might experience availability issues for requests that depend on that specific data or component, while the affected nodes are being restarted.
+
+Refer to [Plan for production](/deploy-manage/deploy/elastic-cloud/elastic-cloud-hosted-planning.md) for more information about High Availability (HA) on ECH.
+
 ## Perform the upgrade [perform-cloud-upgrade]
 
 Log in to your {{ecloud}} environment:

manage-data/lifecycle/curator.md

@@ -2,7 +2,6 @@
 navigation_title: Curator
 applies_to:
   stack: ga
-  serverless: ga
 ---
 
 # Elasticsearch Curator

manage-data/lifecycle/data-tiers.md

@@ -5,7 +5,6 @@ mapped_pages:
   - https://www.elastic.co/guide/en/cloud/current/ec-disable-data-tier.html
 applies_to:
   stack: ga
-  serverless: ga
 products:
   - id: elasticsearch
   - id: cloud-enterprise

manage-data/lifecycle/index-lifecycle-management/configure-lifecycle-policy.md

@@ -4,7 +4,6 @@ mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/set-up-lifecycle-policy.html
 applies_to:
   stack: ga
-  serverless: ga
 products:
   - id: elasticsearch
 ---

manage-data/lifecycle/index-lifecycle-management/index-lifecycle.md

@@ -4,7 +4,6 @@ mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/ilm-index-lifecycle.html
 applies_to:
   stack: ga
-  serverless: ga
 products:
   - id: elasticsearch
 ---