Merge branch 'main' into issue-2281-ea

Author: natasha-moore-elastic

.github/CODEOWNERS

@@ -9,19 +9,19 @@
 # The docs
 /cloud-account/                             @elastic/admin-docs
 /deploy-manage/                             @elastic/admin-docs
-/explore-analyze/                           @elastic/core-docs @elastic/experience-docs 
+/explore-analyze/                           @elastic/core-docs @elastic/experience-docs
 /extend/                                    @elastic/core-docs
-/get-started/                               @elastic/core-docs
+/get-started/                               @elastic/core-docs @elastic/project-docs
 
 /manage-data/                               @elastic/admin-docs
-/manage-data/data-store/                    @elastic/admin-docs @elastic/developer-docs 
+/manage-data/data-store/                    @elastic/admin-docs @elastic/developer-docs
 /manage-data/ingest/                        @elastic/ingest-docs
 
 /reference/                                 @elastic/docs
 /reference/apm-agents/                      @elastic/ingest-docs
 /reference/data-analysis/                   @elastic/docs
 /reference/data-analysis/observability/     @elastic/experience-docs
-/reference/data-analysis/kibana/            @elastic/experience-docs 
+/reference/data-analysis/kibana/            @elastic/experience-docs
 /reference/data-analysis/machine-learning/  @elastic/developer-docs
 /reference/data-analysis/observability/     @elastic/experience-docs
 /reference/elasticsearch/clients/           @elastic/developer-docs
@@ -35,24 +35,30 @@
 /release-notes/                             @elastic/docs
 
 /release-notes/apm-agents/                  @elastic/ingest-docs
-/release-notes/elastic-cloud-serverless/    @elastic/admin-docs
+/release-notes/elastic-cloud-serverless/    @elastic/admin-docs @elastic/docs-serverless-release-team
 /release-notes/elastic-observability/       @elastic/ski-docs
 /release-notes/elastic-security/            @elastic/ski-docs
 /release-notes/elasticsearch-clients/       @elastic/developer-docs
 /release-notes/fleet-elastic-agent/         @elastic/ingest-docs
 /release-notes/intro/                       @elastic/docs
 
-/solutions/                                 @elastic/experience-docs @elastic/developer-docs 
+/solutions/                                 @elastic/experience-docs @elastic/developer-docs
 /solutions/observability/                   @elastic/experience-docs
-/solutions/observability/get-started/       @elastic/ski-docs
+/solutions/observability/apm/apm-agents/    @elastic/ingest-docs
+/solutions/observability/apm/apm-server/    @elastic/ingest-docs
+/solutions/observability/apm/ingest/        @elastic/ingest-docs
+/solutions/observability/apm/opentelemetry/ @elastic/ingest-docs
+/solutions/observability/get-started/       @elastic/ski-docs @elastic/project-docs
 /solutions/search/                          @elastic/developer-docs
+/solutions/search/get-started/              @elastic/developer-docs @elastic/project-docs
 /solutions/security/                        @elastic/experience-docs
+/solutions/security/get-started             @elastic/experience-docs @elastic/project-docs
 
 /troubleshoot/                              @elastic/docs
 /troubleshoot/deployments/                  @elastic/admin-docs
 /troubleshoot/elasticsearch/                @elastic/admin-docs
 /troubleshoot/ingest/                       @elastic/ingest-docs
-/troubleshoot/kibana/                       @elastic/admin-docs @elastic/experience-docs 
+/troubleshoot/kibana/                       @elastic/admin-docs @elastic/experience-docs
 /troubleshoot/monitoring/                   @elastic/admin-docs @elastic/experience-docs
 /troubleshoot/observability/                @elastic/ski-docs
 /troubleshoot/security/                     @elastic/ski-docs

.github/workflows/co-docs-builder.yml

@@ -21,7 +21,7 @@ on:
 jobs:
   publish:
     if: contains(github.event.pull_request.labels.*.name, 'ci:doc-build')
-    uses: elastic/workflows/.github/workflows/docs-versioned-publish.yml@main
+    uses: elastic/dev-docs-workflows/.github/workflows/docs-versioned-publish.yml@main
     with:
       # Refers to Vercel project
       project-name: elastic-dot-co-docs-preview-docs

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

@@ -0,0 +1,106 @@
+name: Update Kube Stack Version
+
+on:
+  schedule:
+    # Run every Monday at 9:00 AM UTC
+    - cron: '0 9 * * 1'
+  workflow_dispatch:
+    inputs:
+      dry_run:
+        description: 'Dry run (check for updates without creating PR)'
+        required: false
+        default: false
+        type: boolean
+
+jobs:
+  update-kube-stack-version:
+    runs-on: ubuntu-latest
+    
+    steps:
+    - name: Checkout repository
+      uses: actions/checkout@v5
+      with:
+        token: ${{ secrets.GITHUB_TOKEN }}
+        fetch-depth: 0
+
+    - name: Set up Python
+      uses: actions/setup-python@v5
+      with:
+        python-version: '3.13'
+
+    - name: Install dependencies
+      run: |
+        python -m pip install --upgrade pip
+        pip install requests
+
+    - name: Run update script
+      id: update-script
+      run: |
+        echo "Running kube-stack-version update script..."
+        python scripts/update_kube_stack_version.py
+        echo "Script completed successfully"
+
+    - name: Check for changes
+      id: check-changes
+      run: |
+        if git diff --quiet HEAD -- docset.yml; then
+          echo "No changes detected in docset.yml"
+          echo "has_changes=false" >> $GITHUB_OUTPUT
+        else
+          echo "Changes detected in docset.yml"
+          echo "has_changes=true" >> $GITHUB_OUTPUT
+          
+          # Show the diff for logging
+          echo "Changes:"
+          git diff HEAD -- docset.yml
+        fi
+
+    - name: Create Pull Request
+      if: steps.check-changes.outputs.has_changes == 'true' && github.event.inputs.dry_run != 'true'
+      uses: peter-evans/create-pull-request@v7
+      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 `docset.yml` based on the latest version from the elastic-agent repository.
+          
+          **Changes:**
+          - Updated `kube-stack-version` to the latest value from elastic-agent repository
+          
+          **Generated by:** [Update Kube Stack Version workflow](https://github.com/${{ github.repository }}/actions/workflows/update-kube-stack-version.yml)
+          
+          This is an automated update. Please review the changes before merging.
+        branch: update-kube-stack-version
+        delete-branch: true
+        labels: |
+          automated
+          chore
+          kube-stack-version
+
+    - name: Dry run summary
+      if: github.event.inputs.dry_run == 'true'
+      run: |
+        echo "## Dry Run Summary" >> $GITHUB_STEP_SUMMARY
+        echo "" >> $GITHUB_STEP_SUMMARY
+        if [ "${{ steps.check-changes.outputs.has_changes }}" == "true" ]; then
+          echo "✅ **Changes detected** - A PR would be created in a real run" >> $GITHUB_STEP_SUMMARY
+          echo "" >> $GITHUB_STEP_SUMMARY
+          echo "**Changes that would be made:**" >> $GITHUB_STEP_SUMMARY
+          echo '```diff' >> $GITHUB_STEP_SUMMARY
+          git diff HEAD -- docset.yml >> $GITHUB_STEP_SUMMARY
+          echo '```' >> $GITHUB_STEP_SUMMARY
+        else
+          echo "ℹ️ **No changes needed** - kube-stack-version is already up to date" >> $GITHUB_STEP_SUMMARY
+        fi
+
+    - name: Summary
+      if: github.event.inputs.dry_run != 'true'
+      run: |
+        echo "## Update Summary" >> $GITHUB_STEP_SUMMARY
+        echo "" >> $GITHUB_STEP_SUMMARY
+        if [ "${{ steps.check-changes.outputs.has_changes }}" == "true" ]; then
+          echo "✅ **PR Created** - Changes detected and pull request created" >> $GITHUB_STEP_SUMMARY
+        else
+          echo "ℹ️ **No changes needed** - kube-stack-version is already up to date" >> $GITHUB_STEP_SUMMARY
+        fi

.gitignore

@@ -2,6 +2,10 @@
 .artifacts
 .DS_store
 
+# Jetbrains files
+.idea
+*.iml
+
 # Add LLM/AI related files
 AGENTS.md
 .github/copilot-instructions.md

deploy-manage/_snippets/autoops-cc-ech-faq.md

@@ -1,3 +1,3 @@
 This path is not supported. Currently, we only support using Cloud Connect to connect ECE, ECK, and self-managed clusters to AutoOps.
 
-For {{ech}} clusters, AutoOps is set up and enabled automatically in all supported [regions](/deploy-manage/monitor/autoops/ec-autoops-regions.md), and can be [accessed](/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md) from the deployment overview page.
+For {{ech}} clusters, AutoOps is set up and enabled automatically in all supported [regions](/deploy-manage/monitor/autoops/ec-autoops-regions.md), and can be [accessed](/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md#ec-autoops-how-to-access) from the deployment overview page.

deploy-manage/_snippets/autoops-cc-payment-faq.md

@@ -1 +1 @@
-Using [AutoOps for ECE, ECK, and self-managed clusters](/deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected.md) through Cloud Connect is included with your [self-managed Enterprise license](https://www.elastic.co/subscriptions).
+Using [AutoOps for ECE, ECK, and self-managed clusters](/deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected.md) through Cloud Connect is included with your [self-managed Enterprise license](https://www.elastic.co/subscriptions) and self-managed free trials. 

deploy-manage/api-keys.md

@@ -6,9 +6,10 @@ applies_to:
     ece: ga
     self: ga
   serverless: ga
+navigation_title: API keys
 ---
 
-# API keys
+# Elastic API keys
 
 API keys are security mechanisms used to authenticate and authorize access to your deployments and {{es}} resources. 
 

deploy-manage/autoscaling/trained-model-autoscaling.md

@@ -133,8 +133,8 @@ In case of ingest-optimized deployments, we maximize the number of model allocat
 | Level | Allocations | Threads | VCUs |
 | --- | --- | --- | --- |
 | Low | 0 to 2 dynamically | 1 | 0 to 16 dynamically |
-| Medium | 1 to 32 dynamically | 1 | 8 to 256 dynamically |
-| High | 1 to 512 for Search<br> 1 to 128 for Security and Observability<br> | 1 | 8 to 4096 for Search<br> 8 to 1024 for Security and Observability<br> |
+| Medium | 0 to 32 dynamically | 1 | 8 to 256 dynamically |
+| High | 0 to 512 for Search<br> 1 to 128 for Security and Observability<br> | 1 | 8 to 4096 for Search<br> 8 to 1024 for Security and Observability<br> |
 
 :::
 

deploy-manage/cloud-connect.md

@@ -23,11 +23,11 @@ Learn how to set up and use [](/deploy-manage/monitor/autoops/cc-autoops-as-clou
 
 Find answers to your questions about Cloud Connect.
 
-* [Does using Cloud Connect require additional payment?](#cc-additional-payment)
+* [Does Cloud Connect require additional payment?](#cc-additional-payment)
 * [Can I use Cloud Connect to connect my Elastic Cloud Hosted clusters to AutoOps?](#cc-ech)
 * [Are more services going to be available with Cloud Connect?](#cc-more-services)
 
-$$$cc-additional-payment$$$ **Does using Cloud Connect require additional payment?** 
+$$$cc-additional-payment$$$ **Does Cloud Connect require additional payment?** 
 :   Each cloud connected service has its own licensing and payment requirements. 
     :::{include} /deploy-manage/_snippets/autoops-cc-payment-faq.md
 ::: 

deploy-manage/cloud-organization/billing/billing-faq.md

@@ -3,6 +3,9 @@ mapped_pages:
   - https://www.elastic.co/guide/en/cloud/current/ec-faq-billing.html
 applies_to:
   deployment:
+    self:
+    ece:
+    eck:
     ess: all
   serverless: all
 products:
@@ -29,6 +32,7 @@ This frequently-asked-questions list answers some of your more common questions
 * [How can I delete my {{ecloud}} account?](#faq-deleteaccount)
 * [Can I get a refund?](#faq-refund)
 * [What is included in my paid {{ecloud}} deployment?](#faq-included)
+* [Does Cloud Connect require additional payment?](#billing-cc-additional-payment)
 * [What are the data transfer and storage charges and how can I control them?](#faq-dts)
 * [What taxes will be applied on my invoice?](#faq-taxes)
 
@@ -94,6 +98,9 @@ $$$faq-deleteaccount$$$How can I delete my {{ecloud}} account?
 $$$faq-refund$$$Can I get a refund?
 :   Charges are non-refundable, but once you delete a deployment we’ll stop charging you for that deployment immediately. You only pay for what you use and you can stop using the service at any time. For any special considerations warranting a potential refund, use the {{ecloud}} Console [Support form](https://cloud.elastic.co/support?page=docs&placement=docs-body) to open a support case and select *Billing issue* as the category. To ensure quick processing, be sure to provide detail about the reasons for the refund request as well as other matters pertaining to the issue. For other ways to open a Support case, check [Contact us](../../../troubleshoot/index.md).
 
+$$$billing-cc-additional-payment$$$ **Does Cloud Connect require additional payment?** 
+:   Each cloud connected service has its own licensing and payment requirements. For more information, refer to the [Elastic self-managed subscriptions](https://www.elastic.co/subscriptions) page.
+
 $$$faq-included$$$What is included in my paid {{ech}} deployment?
 :   All subscription tiers for {{ech}} include the following free allowance: