查看集群见解 - Amazon EKS
查看配置见解（控制台）查看升级见解（控制台）查看集群见解（AWS CLI）

帮助改进此页面

要帮助改进本用户指南，请选择位于每个页面右侧窗格中的在 GitHub 上编辑此页面链接。

查看集群见解

Amazon EKS 提供两种类型的见解：配置见解与升级见解。配置见解可识别 EKS 混合节点设置中可能损害集群或工作负载功能的错误配置。升级见解可识别可能影响您升级到新版 Kubernetes 能力的问题。

要查看已执行的见解检查列表以及 Amazon EKS 发现的任何相关问题，您可以调用 AWS Management Console、AWS CLI、AWS SDK 和 Amazon EKS ListInsights API 操作进行查看。

查看配置见解（控制台）

  1. 打开 Amazon EKS console 控制台。

  2. 从集群列表中，选择您希望查看见解的 Amazon EKS 集群的名称。

  3. 选择监控集群。

  4. 选择集群运行状况选项卡。

  5. 在配置见解表中，您将看到以下列：

    • 名称 – Amazon EKS 对集群执行的检查。

    • 见解状态：状态为 Error 的见解表示存在可能影响集群功能的错误配置。状态为 Warning 的见解表示配置与记录的方法不匹配，但如果有意配置该集群功能，则可能会起作用。状态为 Passing 的见解表示 Amazon EKS 并未在集群中发现与该见解检查相关的任何问题。

    • 描述 – 来自见解检查的信息，包括警报和建议的补救措施。

    • 上次刷新时间：此集群上次刷新见解状态的时间。

查看升级见解（控制台）

  1. 打开 Amazon EKS console 控制台。

  2. 从集群列表中，选择您希望查看见解的 Amazon EKS 集群的名称。

  3. 选择查看控制面板。

  4. 选择集群见解选项卡。

  5. 在升级见解表中，您将看到以下列：

    • 名称：Amazon EKS 对集群执行的检查。

    • 见解状态 – 状态为“错误”的见解通常表示受影响的 Kubernetes 版本是当前集群版本的 N+1，而状态为“警告”的见解表示该见解适用于未来 Kubernetes 版本 N+2 或更高版本。状态为“通过”的见解表示 Amazon EKS 在您的集群中未发现与该见解检查相关的任何问题。状态为“未知”的见解表示 Amazon EKS 无法确定您的集群是否受到此见解检查的影响。

    • 版本 – 见解检查可能存在问题的 Kubernetes 版本。

    • 上次刷新时间：此集群上次刷新见解状态的时间。

    • 上次转换时间：此见解上次更改状态的时间。

    • 描述 – 来自见解检查的信息，包括警报和建议的补救措施。

查看集群见解（AWS CLI）

  1. 确定您要检查哪个集群以获取见解。以下命令列出指定集群的见解。根据需要对该命令进行以下修改，然后运行修改后的命令：

    • 将 region-code 替换为 AWS 区域的代码。

    • 将 my-cluster 替换为您的集群的名称。

      aws eks list-insights --region region-code --cluster-name my-cluster

      示例输出如下。

      {
"insights":
    [
        {
            "id": "a1b2c3d4-5678-90ab-cdef-EXAMPLE11111",
            "name": "Deprecated APIs removed in Kubernetes vX.XX",
            "category": "UPGRADE_READINESS",
            "kubernetesVersion": "X.XX",
            "lastRefreshTime": 1734557315.000,
            "lastTransitionTime": 1734557309.000,
            "description": "Checks for usage of deprecated APIs that are scheduled for removal in Kubernetes vX.XX. Upgrading your cluster before migrating to the updated APIs supported by vX.XX could cause application impact.",
            "insightStatus":
            {
                "status": "PASSING",
                "reason": "No deprecated API usage detected within the last 30 days.",
            },
        },
        {
            "id": "a1b2c3d4-5678-90ab-cdef-EXAMPLE22222",
            "name": "Kubelet version skew",
            "category": "UPGRADE_READINESS",
            "kubernetesVersion": "X.XX",
            "lastRefreshTime": 1734557309.000,
            "lastTransitionTime": 1734557309.000,
            "description": "Checks for kubelet versions of worker nodes in the cluster to see if upgrade would cause non compliance with supported Kubernetes kubelet version skew policy.",
            "insightStatus":
            {
                "status": "UNKNOWN",
                "reason": "Unable to determine status of node kubelet versions.",
            },
        },
        {
            "id": "a1b2c3d4-5678-90ab-cdef-EXAMPLE33333",
            "name": "Deprecated APIs removed in Kubernetes vX.XX",
            "category": "UPGRADE_READINESS",
            "kubernetesVersion": "X.XX",
            "lastRefreshTime": 1734557315.000,
            "lastTransitionTime": 1734557309.000,
            "description": "Checks for usage of deprecated APIs that are scheduled for removal in Kubernetes vX.XX. Upgrading your cluster before migrating to the updated APIs supported by vX.XX could cause application impact.",
            "insightStatus":
            {
                "status": "PASSING",
                "reason": "No deprecated API usage detected within the last 30 days.",
            },
        },
        {
            "id": "a1b2c3d4-5678-90ab-cdef-EXAMPLEaaaaa",
            "name": "Cluster health issues",
            "category": "UPGRADE_READINESS",
            "kubernetesVersion": "X.XX",
            "lastRefreshTime": 1734557314.000,
            "lastTransitionTime": 1734557309.000,
            "description": "Checks for any cluster health issues that prevent successful upgrade to the next Kubernetes version on EKS.",
            "insightStatus":
            {
                "status": "PASSING",
                "reason": "No cluster health issues detected.",
            },
        },
        {
            "id": "a1b2c3d4-5678-90ab-cdef-EXAMPLEbbbbb",
            "name": "EKS add-on version compatibility",
            "category": "UPGRADE_READINESS",
            "kubernetesVersion": "X.XX",
            "lastRefreshTime": 1734557314.000,
            "lastTransitionTime": 1734557309.000,
            "description": "Checks version of installed EKS add-ons to ensure they are compatible with the next version of Kubernetes. ",
            "insightStatus": { "status": "PASSING", "reason": "All installed EKS add-on versions are compatible with next Kubernetes version."},
        },
        {
            "id": "a1b2c3d4-5678-90ab-cdef-EXAMPLEccccc",
            "name": "kube-proxy version skew",
            "category": "UPGRADE_READINESS",
            "kubernetesVersion": "X.XX",
            "lastRefreshTime": 1734557314.000,
            "lastTransitionTime": 1734557309.000,
            "description": "Checks version of kube-proxy in cluster to see if upgrade would cause non compliance with supported Kubernetes kube-proxy version skew policy.",
            "insightStatus":
            {
                "status": "PASSING",
                "reason": "kube-proxy versions match the cluster control plane version.",
            },
        },
        {
            "id": "a1b2c3d4-5678-90ab-cdef-EXAMPLEddddd",
            "name": "Deprecated APIs removed in Kubernetes vX.XX",
            "category": "UPGRADE_READINESS",
            "kubernetesVersion": "X.XX",
            "lastRefreshTime": 1734557315.000,
            "lastTransitionTime": 1734557309.000,
            "description": "Checks for usage of deprecated APIs that are scheduled for removal in Kubernetes vX.XX. Upgrading your cluster before migrating to the updated APIs supported by vX.XX could cause application impact.",
            "insightStatus":
            {
                "status": "PASSING",
                "reason": "No deprecated API usage detected within the last 30 days.",
            },
        },
    ],
"nextToken": null,
}

  2. 有关见解的描述性信息，请运行以下命令。根据需要对该命令进行以下修改，然后运行修改后的命令：

    • 将 region-code 替换为 AWS 区域的代码。

    • 请将 a1b2c3d4-5678-90ab-cdef-EXAMPLE22222 替换为从集群见解列表中检索到的见解 ID。

    • 将 my-cluster 替换为您的集群的名称。

      aws eks describe-insight --region region-code --id a1b2c3d4-5678-90ab-cdef-EXAMPLE22222 --cluster-name my-cluster

      示例输出如下。

      {
  "insight":
    {
      "id": "a1b2c3d4-5678-90ab-cdef-EXAMPLE22222",
      "name": "Kubelet version skew",
      "category": "UPGRADE_READINESS",
      "kubernetesVersion": "1.27",
      "lastRefreshTime": 1734557309.000,
      "lastTransitionTime": 1734557309.000,
      "description": "Checks for kubelet versions of worker nodes in the cluster to see if upgrade would cause non compliance with supported Kubernetes kubelet version skew policy.",
      "insightStatus":
        {
          "status": "UNKNOWN",
          "reason": "Unable to determine status of node kubelet versions.",
        },
      "recommendation": "Upgrade your worker nodes to match the Kubernetes version of your cluster control plane.",
      "additionalInfo":
        {
          "Kubelet version skew policy": "https://kubernetes.io/releases/version-skew-policy/#kubelet",
          "Updating a managed node group": "https://docs.aws.amazon.com/eks/latest/userguide/update-managed-node-group.html",
        },
      "resources": [],
      "categorySpecificSummary":
        { "deprecationDetails": [], "addonCompatibilityDetails": [] },
    },
}