2

在此处输入图像描述

我想在 HPA 上使用 pod 网络接收字节计数标准 kubernetes 指标。使用以下 yaml 来完成此操作，但出现无法从自定义指标 API 获取指标等错误：未注册自定义指标 API (custom.metrics.k8s.io)

apiVersion: autoscaling/v2beta1
kind: HorizontalPodAutoscaler
metadata:
  name: xxxx-hoa
  namespace: xxxxx
spec:
  scaleTargetRef:
    apiVersion: apps/v1beta1
    kind: Deployment
    name: xxxx-xxx
  minReplicas: 2
  maxReplicas: 6
  metrics:
  - type: Pods
    pods:
      metricName: received_bytes_count
      targetAverageValue: 20k

如果有人有使用相同类型指标的经验，那将非常有帮助

在此处输入图像描述

4

2 回答 2

1

autoscaling/v1 是一个 API，用于仅基于 CPU 利用率进行自动缩放。因此，为了根据其他指标进行自动缩放，您应该使用 autoscaling/v2beta2。我建议您阅读此文档以检查 API 版本。

于 2020-11-07T23:10:56.000 回答
1

解决方案

要使其正常工作，您需要部署Stackdriver Custom Metrics Adapter。下面的命令来部署它。

$ kubectl create clusterrolebinding cluster-admin-binding \
    --clusterrole cluster-admin --user "$(gcloud config get-value account)"

$ kubectl apply -f https://raw.githubusercontent.com/GoogleCloudPlatform/k8s-stackdriver/master/custom-metrics-stackdriver-adapter/deploy/production/adapter_new_resource_model.yaml

稍后您需要使用正确的Custom Metric，在您的情况下应该是kubernetes.io|pod|network|received_bytes_count

描述

在Autoscaling 工作负载的自定义和外部指标文档中，您拥有需要部署的信息，StackDriver Adapter然后才能获得自定义指标。

在您可以使用自定义指标之前，您必须在您的 Google Cloud 项目中启用监控并在您的集群上安装 Stackdriver 适配器。

下一步是部署您的应用程序（我使用 Nginx 部署进行测试）并创建适当的 HPA。

在您的 HPA 示例中，您有一些问题

apiVersion: autoscaling/v2beta1 ## you can also use autoscaling/v2beta2 if you need more features, however for this scenario is ok
kind: HorizontalPodAutoscaler
metadata:
  name: xxxx-hoa
  namespace: xxxxx # HPA have namespace specified, deployment doesnt have
spec:
  scaleTargetRef:
    apiVersion: apps/v1beta1 # apiVersion: apps/v1beta1 is quite old. In Kubernetes 1.16+ it was changed to apps/v1
    kind: Deployment
    name: xxxx-xxx
  minReplicas: 2
  maxReplicas: 6
  metrics:
  - type: Pods
    pods:
      metricName: received_bytes_count # this metrics should be replaced with kubernetes.io|pod|network|received_bytes_count
      targetAverageValue: 20k

在 GKE 中，您可以在 和 之间进行autoscaling/v2beta1选择autoscaling/v2beta2。您的情况适用于两者apiVersions，但是如果您决定使用autoscaling/v2beta2，则需要更改清单语法。

为什么kubernetes.io/pod/network/received_bytes_count？您指的是 Kubernetes 指标，并/pod/network/received_bytes_count在本文档中提供。

为什么|而不是/？如果您查看Github 上的 Stackdriver 文档，您会找到相关信息。

Stackdriver 指标有一种由“/”字符分隔的路径形式，但自定义指标 API 禁止使用“/”字符。使用自定义指标 - Stackdriver Adapter 时，直接通过自定义指标 API 或通过在 HPA 中指定自定义指标，将“/”字符替换为“|”。例如，要使用 custom.googleapis.com/my/custom/metric，请指定 custom.googleapis.com|my|custom|metric。

正确配置

对于 v2beta1

apiVersion: autoscaling/v2beta1
kind: HorizontalPodAutoscaler
metadata:
  name: xxxx-hoa
spec:
  scaleTargetRef:
    apiVersion: apps/v1 # In your case should be apps/v1beta1 but my deployment was created with apps/v1 apiVersion
    kind: Deployment
    name: nginx
  minReplicas: 2
  maxReplicas: 6
  metrics:
  - type: Pods
    pods:
      metricName: "kubernetes.io|pod|network|received_bytes_count"
      targetAverageValue: 20k

对于 v2beta2

apiVersion: autoscaling/v2beta2
kind: HorizontalPodAutoscaler
metadata:
  name: xxxx-hoa
  namespace: default
spec:
  scaleTargetRef:
    apiVersion: apps/v1
    kind: Deployment
    name: nginx
  minReplicas: 2
  maxReplicas: 6
  metrics:
  - type: Pods
    pods:
      metric:
        name: "kubernetes.io|pod|network|received_bytes_count"
      target:
        type: AverageValue
        averageValue: 20k

测试输出

Conditions:
  Type            Status  Reason            Message
  ----            ------  ------            -------
  AbleToScale     True    SucceededRescale  the HPA controller was able to update the target scale to 2
  ScalingActive   True    ValidMetricFound  the HPA was able to successfully calculate a replica count from pods metric kubernetes.io|pod|network|received_bytes_count
  ScalingLimited  True    TooFewReplicas    the desired replica count is more than the maximum replica count
Events:
  Type    Reason             Age                 From                       Message
  ----    ------             ----                ----                       -------
  Normal  SuccessfulRescale  8m18s               horizontal-pod-autoscaler  New size: 4; reason: pods metric kubernetes.io|pod|network|received_bytes_count above target
  Normal  SuccessfulRescale  8m9s                horizontal-pod-autoscaler  New size: 6; reason: pods metric kubernetes.io|pod|network|received_bytes_count above target
  Normal  SuccessfulRescale  17s                 horizontal-pod-autoscaler  New size: 5; reason: All metrics below target
  Normal  SuccessfulRescale  9s (x2 over 8m55s)  horizontal-pod-autoscaler  New size: 2; reason: All metrics below target

当前配置可能存在的问题

在您的 HPA 中，您已经指定了命名空间，但在您的目标部署中没有。HPA 和部署都应该具有相同的命名空间。使用此不匹配配置，您可能会遇到以下问题：

Conditions:
  Type         Status  Reason          Message
  ----         ------  ------          -------
  AbleToScale  False   FailedGetScale  the HPA controller was unable to get the target's current scale: deployments/scale.apps "nginx" not found
Events:
  Type     Reason          Age                  From                       Message
  ----     ------          ----                 ----                       -------
  Warning  FailedGetScale  94s (x264 over 76m)  horizontal-pod-autoscaler  deployments/scale.apps "nginx" not found

在 Kubernetes 1.16+ 中，部署使用apiVersion: apps/v1，您将无法apiVersion: apps/v1beta1在 Kubernetes 1.16+中创建部署

于 2020-11-18T14:10:30.500 回答