From 459003b831dcc5cf1090782df20e19afa82ab90b Mon Sep 17 00:00:00 2001 From: Michael Montgomery Date: Thu, 26 Feb 2026 13:29:31 -0600 Subject: [PATCH 1/4] Update AutoOps + ECK docs for removal of enterprise license requirement. Signed-off-by: Michael Montgomery --- ...autoops-sm-troubleshoot-eck-no-clusters.md | 36 +++++++++++++++++++ ...c-cloud-connect-autoops-troubleshooting.md | 6 ++++ .../cc-connect-self-managed-to-autoops.md | 8 +++++ .../monitor/autoops/ec-autoops-faq.md | 6 ++-- 4 files changed, 54 insertions(+), 2 deletions(-) diff --git a/deploy-manage/monitor/autoops/autoops-sm-troubleshoot-eck-no-clusters.md b/deploy-manage/monitor/autoops/autoops-sm-troubleshoot-eck-no-clusters.md index 59d207d792..69d311eb3d 100644 --- a/deploy-manage/monitor/autoops/autoops-sm-troubleshoot-eck-no-clusters.md +++ b/deploy-manage/monitor/autoops/autoops-sm-troubleshoot-eck-no-clusters.md @@ -127,6 +127,42 @@ If any errors in the logs mention "authorization" or "unauthorized connection", :::{include} ../_snippets/autoops-allowlist-port-and-urls.md ::: +## Verify AutoOps Agent version meets license requirements + +```{applies_to} +eck: ga 3.3.1 +``` + +The minimum AutoOps Agent version depends on your license type. If the agent version is below the minimum for your license, the `AutoOpsAgentPolicy` enters `Invalid` phase. + +| License type | Minimum agent version | +| --- | --- | +| Basic | 9.2.4 | +| Enterprise | 9.2.1 | + +:::::{stepper} + +::::{step} Check the policy status and version +Run the following command. +```shell +kubectl get autoopsagentpolicy -o jsonpath='{.spec.version}{"\n"}{.status.phase}{"\n"}' +``` +If the status shows `Invalid` with a version-related message, the agent version may not meet the minimum for your license type. +:::: + +::::{step} Check your license type +Run the following command to check the ECK license level. +```shell +kubectl get configmap elastic-licensing -n -o jsonpath='{.data.eck_license_level}' +``` +:::: + +::::{step} Upgrade the agent if necessary +If your license type is Basic and your agent version is below 9.2.4, upgrade the AutoOps Agent to version 9.2.4 or later. +:::: + +::::: + ## Check cluster health Ensure that the {{es}} clusters you are trying to connect to AutoOps are healthy. {{agent}} may fail to connect clusters in a Red state. \ No newline at end of file diff --git a/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md b/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md index d731bc8637..2c4956ac92 100644 --- a/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md +++ b/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md @@ -25,6 +25,7 @@ Use this guide to troubleshoot any issues you may encounter. * [My organization's firewall might be preventing {{agent}} from collecting and sending metrics.](#firewall) * [{{agent}} is failing to connect because it doesn't recognize my SSL certificate.](#custom-cert) * [I went through the wizard with {{ECK}} (ECK) as my installation method, but I can't view any connected clusters in my account.](#eck-no-clusters) {applies_to}`eck: ga 3.3` +* [My `AutoOpsAgentPolicy` entered an `Invalid` phase after a license change.](#invalid-phase-license-change) {applies_to}`eck: ga 3.3.1` $$$single-cloud-org$$$**I’m trying to create a Cloud organization, but I’m already part of a different one.** : :::{include} /deploy-manage/monitor/_snippets/single-cloud-org.md @@ -52,6 +53,11 @@ $$$custom-cert$$$**{{agent}} is failing to connect because it doesn't recognize $$$eck-no-clusters$$$**I went through the wizard with {{ECK}} (ECK) as my installation method, but I can't view any connected clusters in my account.** {applies_to}`eck: ga 3.3` : Refer to [](/deploy-manage/monitor/autoops/autoops-sm-troubleshoot-eck-no-clusters.md) to diagnose and resolve common issues. +$$$invalid-phase-license-change$$$**My `AutoOpsAgentPolicy` entered an `Invalid` phase after a license change.** {applies_to}`eck: ga 3.3.1` +: The minimum AutoOps Agent version depends on your license type. Enterprise licenses support agent versions 9.2.1 and later, while Basic licenses require 9.2.4 or later. If your license is downgraded from Enterprise to Basic and your AutoOps Agent version is between 9.2.1 and 9.2.3, the policy will fail validation and enter an `Invalid` phase. + + To resolve this, upgrade the AutoOps Agent to version 9.2.4 or later. Refer to the [prerequisites](/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md#prerequisites) for the full version requirements. + ## Run the AutoOps Connectivity Check Run the [AutoOps Connectivity Check](../autoops/autoops-connectivity-check.md) to test your system and diagnose any issues that might prevent you from connecting your cluster to AutoOps. diff --git a/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md b/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md index 95cfba1b40..6a63fb5f21 100644 --- a/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md +++ b/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md @@ -30,6 +30,14 @@ Ensure your system meets the following requirements before proceeding: * Your cluster is on a [supported {{es}} version](https://www.elastic.co/support/eol) (7.17.x and above). * The agent you install for the connection is allowed to send metrics to {{ecloud}}. * {applies_to}`eck: ga 3.3` To install {{agent}} using ECK, your ECK operator is on version 3.3.0 and above. +* {applies_to}`eck: ga 3.3.1` The AutoOps Agent version meets the minimum for your license type: + * **Basic license**: 9.2.4 or later. + * **Enterprise license**: 9.2.1 or later. + +:::{important} +:applies_to: { eck: ga 3.3.1 } +If you are running an Enterprise license with an AutoOps Agent version between 9.2.1 and 9.2.3, and your license is later downgraded to Basic, the `AutoOpsAgentPolicy` will enter an `Invalid` phase. To resolve this, upgrade the AutoOps Agent to version 9.2.4 or later. +::: ## Connect to AutoOps [connect-to-autoops] diff --git a/deploy-manage/monitor/autoops/ec-autoops-faq.md b/deploy-manage/monitor/autoops/ec-autoops-faq.md index f3fb2f8b36..10d37fbcf0 100644 --- a/deploy-manage/monitor/autoops/ec-autoops-faq.md +++ b/deploy-manage/monitor/autoops/ec-autoops-faq.md @@ -75,7 +75,9 @@ $$$autoops-issue-resolution$$$**Can AutoOps automatically resolve issues?** : AutoOps only analyzes metrics and is a read-only solution. $$$autoops-supported-versions$$$**Which versions of {{es}} are supported in AutoOps for {{ech}} and ECE, ECK, and self-managed clusters?** -: AutoOps is compatible with [supported {{es}} versions](https://www.elastic.co/support/eol) (7.17.x and above). +: AutoOps is compatible with [supported {{es}} versions](https://www.elastic.co/support/eol) (7.17.x and above). When using the ECK installation method (`AutoOpsAgentPolicy`), the minimum AutoOps Agent version depends on your license type: + * **Basic license**: 9.2.4 or later + * **Enterprise license**: 9.2.1 or later $$$autoops-data-retention$$$**How long does Elastic retain AutoOps data?** : AutoOps has a 10 day retention period. @@ -103,7 +105,7 @@ $$$deployment-types$$$ **Which deployment types can be connected to AutoOps thro : You can connect to AutoOps on a standalone {{stack}}, ECE ({{ece}}), or ECK ({{eck}}) deployment, both on-premise and in private cloud environments. $$$maintenance$$$ **Do I have to do any maintenance when using AutoOps for ECE, ECK, or self-managed clusters?** -: AutoOps is a cloud service, so you don't need to upgrade it yourself. However, we recommend keeping {{agent}} upgraded to the latest version so you can access new features and fixes. +: AutoOps is a cloud service, so you don't need to upgrade it yourself. However, we recommend keeping {{agent}} upgraded to the latest version so you can access new features and fixes. When using the ECK installation method, ensure that your AutoOps Agent version meets the [minimum version requirements](/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md#prerequisites) for your license type. $$$support$$$ **What kind of support is available to me when using AutoOps for ECE, ECK, or self-managed clusters?** : Support eligibility is determined by the license of your connected cluster: From 1e4b475b79310c696795e0b3a2581212bea107a1 Mon Sep 17 00:00:00 2001 From: Michael Montgomery Date: Thu, 26 Feb 2026 14:04:14 -0600 Subject: [PATCH 2/4] Update deploy-manage/monitor/autoops/autoops-sm-troubleshoot-eck-no-clusters.md Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- .../monitor/autoops/autoops-sm-troubleshoot-eck-no-clusters.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/deploy-manage/monitor/autoops/autoops-sm-troubleshoot-eck-no-clusters.md b/deploy-manage/monitor/autoops/autoops-sm-troubleshoot-eck-no-clusters.md index 69d311eb3d..b2092e5b2f 100644 --- a/deploy-manage/monitor/autoops/autoops-sm-troubleshoot-eck-no-clusters.md +++ b/deploy-manage/monitor/autoops/autoops-sm-troubleshoot-eck-no-clusters.md @@ -133,7 +133,7 @@ If any errors in the logs mention "authorization" or "unauthorized connection", eck: ga 3.3.1 ``` -The minimum AutoOps Agent version depends on your license type. If the agent version is below the minimum for your license, the `AutoOpsAgentPolicy` enters `Invalid` phase. +The minimum AutoOps Agent version depends on your license type. If the agent version is below the minimum for your license, the `AutoOpsAgentPolicy` enters the `Invalid` phase. | License type | Minimum agent version | | --- | --- | From 9f9ccf2e7bf49251b2834692ae0b0334b3685139 Mon Sep 17 00:00:00 2001 From: Michael Montgomery Date: Fri, 27 Feb 2026 16:22:48 -0600 Subject: [PATCH 3/4] Review changes. Signed-off-by: Michael Montgomery --- .../autoops-sm-troubleshoot-eck-no-clusters.md | 12 ++++++------ .../cc-cloud-connect-autoops-troubleshooting.md | 6 +++--- 2 files changed, 9 insertions(+), 9 deletions(-) diff --git a/deploy-manage/monitor/autoops/autoops-sm-troubleshoot-eck-no-clusters.md b/deploy-manage/monitor/autoops/autoops-sm-troubleshoot-eck-no-clusters.md index 69d311eb3d..af8792c53d 100644 --- a/deploy-manage/monitor/autoops/autoops-sm-troubleshoot-eck-no-clusters.md +++ b/deploy-manage/monitor/autoops/autoops-sm-troubleshoot-eck-no-clusters.md @@ -127,13 +127,13 @@ If any errors in the logs mention "authorization" or "unauthorized connection", :::{include} ../_snippets/autoops-allowlist-port-and-urls.md ::: -## Verify AutoOps Agent version meets license requirements +## Verify {{agent}} version meets license requirements ```{applies_to} eck: ga 3.3.1 ``` -The minimum AutoOps Agent version depends on your license type. If the agent version is below the minimum for your license, the `AutoOpsAgentPolicy` enters `Invalid` phase. +The minimum required {{agent}} version for the ECK installation method depends on your license type. If the agent version is below the minimum for your license, the `AutoOpsAgentPolicy` resource enters the `Invalid` phase. | License type | Minimum agent version | | --- | --- | @@ -147,18 +147,18 @@ Run the following command. ```shell kubectl get autoopsagentpolicy -o jsonpath='{.spec.version}{"\n"}{.status.phase}{"\n"}' ``` -If the status shows `Invalid` with a version-related message, the agent version may not meet the minimum for your license type. +If the status is `Invalid` with a version-related message, {{agent}} does not meet the minimum version requirement for your license type. :::: ::::{step} Check your license type -Run the following command to check the ECK license level. +Run the following command to check your cluster's license type. ```shell kubectl get configmap elastic-licensing -n -o jsonpath='{.data.eck_license_level}' ``` :::: -::::{step} Upgrade the agent if necessary -If your license type is Basic and your agent version is below 9.2.4, upgrade the AutoOps Agent to version 9.2.4 or later. +::::{step} Upgrade {{agent}} +Based on your findings in the previous steps, upgrade {{agent}} to the appropriate version. :::: ::::: diff --git a/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md b/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md index 2c4956ac92..228ac947f1 100644 --- a/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md +++ b/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md @@ -25,7 +25,7 @@ Use this guide to troubleshoot any issues you may encounter. * [My organization's firewall might be preventing {{agent}} from collecting and sending metrics.](#firewall) * [{{agent}} is failing to connect because it doesn't recognize my SSL certificate.](#custom-cert) * [I went through the wizard with {{ECK}} (ECK) as my installation method, but I can't view any connected clusters in my account.](#eck-no-clusters) {applies_to}`eck: ga 3.3` -* [My `AutoOpsAgentPolicy` entered an `Invalid` phase after a license change.](#invalid-phase-license-change) {applies_to}`eck: ga 3.3.1` +* [My `AutoOpsAgentPolicy` resource entered the `Invalid` phase after a license change.](#invalid-phase-license-change) {applies_to}`eck: ga 3.3` $$$single-cloud-org$$$**I’m trying to create a Cloud organization, but I’m already part of a different one.** : :::{include} /deploy-manage/monitor/_snippets/single-cloud-org.md @@ -53,8 +53,8 @@ $$$custom-cert$$$**{{agent}} is failing to connect because it doesn't recognize $$$eck-no-clusters$$$**I went through the wizard with {{ECK}} (ECK) as my installation method, but I can't view any connected clusters in my account.** {applies_to}`eck: ga 3.3` : Refer to [](/deploy-manage/monitor/autoops/autoops-sm-troubleshoot-eck-no-clusters.md) to diagnose and resolve common issues. -$$$invalid-phase-license-change$$$**My `AutoOpsAgentPolicy` entered an `Invalid` phase after a license change.** {applies_to}`eck: ga 3.3.1` -: The minimum AutoOps Agent version depends on your license type. Enterprise licenses support agent versions 9.2.1 and later, while Basic licenses require 9.2.4 or later. If your license is downgraded from Enterprise to Basic and your AutoOps Agent version is between 9.2.1 and 9.2.3, the policy will fail validation and enter an `Invalid` phase. +$$$invalid-phase-license-change$$$**My `AutoOpsAgentPolicy` resource entered the `Invalid` phase after a license change.** {applies_to}`eck: ga 3.3` +: The minimum required {{agent}} version for the ECK installation method depends on your license type. Enterprise licenses support agent versions 9.2.1 and later, and Basic licenses require 9.2.4 or later. If your license is downgraded from Enterprise to Basic and your agent version is between 9.2.1 and 9.2.3, the policy will fail validation and enter the `Invalid` phase. To resolve this, upgrade the AutoOps Agent to version 9.2.4 or later. Refer to the [prerequisites](/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md#prerequisites) for the full version requirements. From 95b8143a2b4f361fd471389aa76c4af74150310e Mon Sep 17 00:00:00 2001 From: Michael Montgomery Date: Fri, 27 Feb 2026 16:56:47 -0600 Subject: [PATCH 4/4] Review fixes Signed-off-by: Michael Montgomery --- .../autoops/cc-cloud-connect-autoops-troubleshooting.md | 4 ++-- .../monitor/autoops/cc-connect-self-managed-to-autoops.md | 4 ++-- deploy-manage/monitor/autoops/ec-autoops-faq.md | 6 ++---- 3 files changed, 6 insertions(+), 8 deletions(-) diff --git a/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md b/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md index 228ac947f1..bcf12fd97a 100644 --- a/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md +++ b/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md @@ -54,9 +54,9 @@ $$$eck-no-clusters$$$**I went through the wizard with {{ECK}} (ECK) as my instal : Refer to [](/deploy-manage/monitor/autoops/autoops-sm-troubleshoot-eck-no-clusters.md) to diagnose and resolve common issues. $$$invalid-phase-license-change$$$**My `AutoOpsAgentPolicy` resource entered the `Invalid` phase after a license change.** {applies_to}`eck: ga 3.3` -: The minimum required {{agent}} version for the ECK installation method depends on your license type. Enterprise licenses support agent versions 9.2.1 and later, and Basic licenses require 9.2.4 or later. If your license is downgraded from Enterprise to Basic and your agent version is between 9.2.1 and 9.2.3, the policy will fail validation and enter the `Invalid` phase. +: The [minimum required {{agent}} version](/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md#prerequisites) for the ECK installation method depends on your license type. Enterprise licenses require agent versions 9.2.1 and later, and Basic licenses require versions 9.2.4 or later. If your license is downgraded from Enterprise to Basic and your agent version is between 9.2.1 and 9.2.3, the policy will fail validation and enter the `Invalid` phase. - To resolve this, upgrade the AutoOps Agent to version 9.2.4 or later. Refer to the [prerequisites](/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md#prerequisites) for the full version requirements. + To resolve this issue, upgrade {{agent}}. ## Run the AutoOps Connectivity Check diff --git a/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md b/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md index 6a63fb5f21..0288b62534 100644 --- a/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md +++ b/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md @@ -30,13 +30,13 @@ Ensure your system meets the following requirements before proceeding: * Your cluster is on a [supported {{es}} version](https://www.elastic.co/support/eol) (7.17.x and above). * The agent you install for the connection is allowed to send metrics to {{ecloud}}. * {applies_to}`eck: ga 3.3` To install {{agent}} using ECK, your ECK operator is on version 3.3.0 and above. -* {applies_to}`eck: ga 3.3.1` The AutoOps Agent version meets the minimum for your license type: +* {applies_to}`eck: ga 3.3.1` The instance of {{agent}} you install meets the version requirements for your license type: * **Basic license**: 9.2.4 or later. * **Enterprise license**: 9.2.1 or later. :::{important} :applies_to: { eck: ga 3.3.1 } -If you are running an Enterprise license with an AutoOps Agent version between 9.2.1 and 9.2.3, and your license is later downgraded to Basic, the `AutoOpsAgentPolicy` will enter an `Invalid` phase. To resolve this, upgrade the AutoOps Agent to version 9.2.4 or later. +If your ECK-managed cluster's license is downgraded, you must upgrade {{agent}} accordingly to avoid your `AutoOpsAgentPolicy` resource becoming invalid. ::: ## Connect to AutoOps [connect-to-autoops] diff --git a/deploy-manage/monitor/autoops/ec-autoops-faq.md b/deploy-manage/monitor/autoops/ec-autoops-faq.md index 10d37fbcf0..45719e65a3 100644 --- a/deploy-manage/monitor/autoops/ec-autoops-faq.md +++ b/deploy-manage/monitor/autoops/ec-autoops-faq.md @@ -75,9 +75,7 @@ $$$autoops-issue-resolution$$$**Can AutoOps automatically resolve issues?** : AutoOps only analyzes metrics and is a read-only solution. $$$autoops-supported-versions$$$**Which versions of {{es}} are supported in AutoOps for {{ech}} and ECE, ECK, and self-managed clusters?** -: AutoOps is compatible with [supported {{es}} versions](https://www.elastic.co/support/eol) (7.17.x and above). When using the ECK installation method (`AutoOpsAgentPolicy`), the minimum AutoOps Agent version depends on your license type: - * **Basic license**: 9.2.4 or later - * **Enterprise license**: 9.2.1 or later +: AutoOps is compatible with [supported {{es}} versions](https://www.elastic.co/support/eol) (7.17.x and above). $$$autoops-data-retention$$$**How long does Elastic retain AutoOps data?** : AutoOps has a 10 day retention period. @@ -105,7 +103,7 @@ $$$deployment-types$$$ **Which deployment types can be connected to AutoOps thro : You can connect to AutoOps on a standalone {{stack}}, ECE ({{ece}}), or ECK ({{eck}}) deployment, both on-premise and in private cloud environments. $$$maintenance$$$ **Do I have to do any maintenance when using AutoOps for ECE, ECK, or self-managed clusters?** -: AutoOps is a cloud service, so you don't need to upgrade it yourself. However, we recommend keeping {{agent}} upgraded to the latest version so you can access new features and fixes. When using the ECK installation method, ensure that your AutoOps Agent version meets the [minimum version requirements](/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md#prerequisites) for your license type. +: AutoOps is a cloud service, so you don't need to upgrade it yourself. However, when using the ECK installation method, make sure your instance of {{agent}} meets the [version requirements](/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md#prerequisites) for your license type. In general, we recommend keeping {{agent}} upgraded to the latest version so you can access new features and fixes. $$$support$$$ **What kind of support is available to me when using AutoOps for ECE, ECK, or self-managed clusters?** : Support eligibility is determined by the license of your connected cluster: