Merge branch 'main' into title-fixes-h1

Author: yetanothertw

.github/workflows/update-kube-stack-version.yml

@@ -0,0 +1,65 @@
+name: Update Kube-Stack Version
+
+on:
+  schedule:
+    # Run every Monday at 9:00 AM UTC
+    - cron: '0 9 * * 1'
+  workflow_dispatch: # Allow manual triggering
+
+jobs:
+  update-kube-stack-version:
+    runs-on: ubuntu-latest
+    
+    steps:
+    - name: Checkout repository
+      uses: actions/checkout@v4
+      with:
+        token: ${{ secrets.GITHUB_TOKEN }}
+    
+    - name: Set up Python
+      uses: actions/setup-python@v4
+      with:
+        python-version: '3.9'
+    
+    - name: Run kube-stack version update script
+      run: |
+        cd scripts
+        python update_kube_stack_version.py
+    
+    - name: Check for changes
+      id: verify-changed-files
+      run: |
+        if [ -n "$(git status --porcelain)" ]; then
+          echo "changed=true" >> $GITHUB_OUTPUT
+        else
+          echo "changed=false" >> $GITHUB_OUTPUT
+        fi
+    
+    - name: Commit and push changes
+      if: steps.verify-changed-files.outputs.changed == 'true'
+      run: |
+        git config --local user.email "[email protected]"
+        git config --local user.name "GitHub Action"
+        git add docs/docset.yml
+        git commit -m "chore: update kube-stack version [skip ci]"
+        git push
+    
+    - name: Create Pull Request
+      if: steps.verify-changed-files.outputs.changed == 'true'
+      uses: peter-evans/create-pull-request@v5
+      with:
+        token: ${{ secrets.GITHUB_TOKEN }}
+        commit-message: "chore: update kube-stack version"
+        title: "chore: update kube-stack version"
+        body: |
+          This PR automatically updates the kube-stack version in `docs/docset.yml` based on the latest version from the elastic-agent repository.
+          
+          **Changes:**
+          - Updated kube-stack version in docset.yml
+          
+          This PR was created automatically by the weekly kube-stack version update workflow.
+        branch: update-kube-stack-version
+        delete-branch: true
+        labels: |
+          automated
+          documentation

deploy-manage/deploy/cloud-enterprise/access-kibana.md

@@ -1,4 +1,5 @@
 ---
+navigation_title: Access {{kib}}
 mapped_pages:
   - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-access-kibana.html
   - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-manage-kibana.html
@@ -9,7 +10,7 @@ products:
   - id: cloud-enterprise
 ---
 
-# Access {{kib}} [ece-access-kibana]
+# Access {{kib}} on {{ece}} [ece-access-kibana]
 
 {{kib}} is an open source analytics and visualization platform designed to search, view, and interact with data stored in {{es}} indices.
 

deploy-manage/deploy/cloud-enterprise/add-plugins.md

@@ -1,11 +1,11 @@
 ---
-navigation_title: Configure plugins and extensions
+navigation_title: Add plugins and extensions
 applies_to:
   deployment:
     ece:
 ---
 
-# Add plugins and extensions [ece-adding-plugins]
+# Add plugins and extensions in {{ece}} [ece-adding-plugins]
 
 Plugins extend the core functionality of {{es}}. {{ece}} makes it easy to add plugins to your deployment by providing a number of plugins that work with your version of {{es}}. One advantage of these plugins is that you generally don’t have to worry about upgrading plugins when upgrading to a new {{es}} version, unless there are breaking changes. The plugins are upgraded along with the rest of your deployment.
 

deploy-manage/deploy/cloud-enterprise/keep-track-of-deployment-activity.md

@@ -1,4 +1,5 @@
 ---
+navigation_title: Keep track of deployment activity
 mapped_pages:
   - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-activity-page.html
 applies_to:
@@ -8,7 +9,7 @@ products:
   - id: cloud-enterprise
 ---
 
-# Keep track of deployment activity [ece-activity-page]
+# Keep track of deployment activity on {{ece}} [ece-activity-page]
 
 The deployment **Activity** page gives you a convenient way to follow all configuration changes that have been applied to your deployment, including which resources were affected, when the changes were applied, who initiated the changes, and whether or not the changes were successful. You can also select **Details** for an expanded, step-by-step view of each change applied to each deployment resource.
 

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

@@ -1,4 +1,5 @@
 ---
+navigation_title: Advanced configuration
 mapped_pages:
   - https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-logstash-advanced-configuration.html
 applies_to:
@@ -8,7 +9,7 @@ products:
   - id: cloud-kubernetes
 ---
 
-# Advanced configuration [k8s-logstash-advanced-configuration]
+# Advanced configuration for {{ls}} on {{eck}} [k8s-logstash-advanced-configuration]
 
 ## Setting JVM options [k8s-logstash-jvm-options]
 

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

@@ -1,4 +1,5 @@
 ---
+navigation_title: Advanced configuration
 mapped_pages:
   - https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-maps-advanced-configuration.html
 applies_to:
@@ -8,7 +9,7 @@ products:
   - id: cloud-kubernetes
 ---
 
-# Advanced configuration [k8s-maps-advanced-configuration]
+# Advanced configuration for Elastic Maps Server on {{eck}} [k8s-maps-advanced-configuration]
 
 ::::{warning}
 This functionality is in technical preview and may be changed or removed in a future release. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features.

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

@@ -1,4 +1,5 @@
 ---
+navigation_title: Advanced configuration
 mapped_pages:
   - https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-apm-advanced-configuration.html
 applies_to:
@@ -8,7 +9,7 @@ products:
   - id: cloud-kubernetes
 ---
 
-# Advanced configuration [k8s-apm-advanced-configuration]
+# Advanced configuration for {{apm-server}} on {{eck}} [k8s-apm-advanced-configuration]
 
 This section covers the following topics:
 

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

@@ -1,4 +1,5 @@
 ---
+navigation_title: Advanced configuration
 mapped_pages:
   - https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-kibana-advanced-configuration.html
 applies_to:
@@ -8,7 +9,7 @@ products:
   - id: cloud-kubernetes
 ---
 
-# Advanced configuration [k8s-kibana-advanced-configuration]
+# Advanced {{kib}} deployment and configuration on {{eck}} [k8s-kibana-advanced-configuration]
 
 If you already looked at the [{{es}} on ECK](elasticsearch-configuration.md) documentation, some of these concepts might sound familiar to you. The resource definitions in ECK share the same philosophy when you want to:
 

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

@@ -1,4 +1,5 @@
 ---
+navigation_title: Quickstart
 mapped_pages:
   - https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-beat-quickstart.html
 applies_to:
@@ -8,7 +9,7 @@ products:
   - id: cloud-kubernetes
 ---
 
-# Quickstart [k8s-beat-quickstart]
+# Quickstart: Running {{beats}} on {{eck}} [k8s-beat-quickstart]
 
 1. Apply the following specification to deploy Filebeat and collect the logs of all containers running in the Kubernetes cluster. ECK automatically configures the secured connection to an {{es}} cluster named `quickstart`, created in [](/deploy-manage/deploy/cloud-on-k8s/elasticsearch-deployment-quickstart.md).
 

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

@@ -1,4 +1,5 @@
 ---
+navigation_title: Quickstart
 mapped_pages:
   - https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-elastic-agent-fleet-quickstart.html
 applies_to:
@@ -8,7 +9,7 @@ products:
   - id: cloud-kubernetes
 ---
 
-# Quickstart [k8s-elastic-agent-fleet-quickstart]
+# Quickstart: Running {{fleet}} on {{eck}} [k8s-elastic-agent-fleet-quickstart]
 
 1. To deploy {{fleet-server}}, {{agents}}, {{es}}, and {{kib}}, apply the following specification: