Kubernetes 1.8.10 kube-apiserver优先级错误

本文介绍了Kubernetes 1.8.10 kube-apiserver优先级错误的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！

问题描述

新的集群1.8.10用kops旋转.

New cluster 1.8.10 spinned with kops.

在K8S 1.8中，有一个新功能Pod Priority and Preemption.详细信息: https: //kubernetes.io/docs/concepts/configuration/pod-priority-preemption/#how-to-use-priority-and-preemption

In K8S 1.8 there is a new feature Pod Priority and Preemption.More information: https://kubernetes.io/docs/concepts/configuration/pod-priority-preemption/#how-to-use-priority-and-preemption

kube-apiserver记录错误

我完全不明白为什么.没有人可以访问它，因为它尚未启用(它是Alpha版).

I quite not understand why. No one should access it as it's not even enabled yet (it's alpha).

没有吊舱正在使用priorityClassName.

运行说明:

这是正常的还是kops特定的?

Is this normal or kops specific?

推荐答案

我认为它与配置(kops get --name $NAME -oyaml)中的Kops选项有关:

I think it is related to that Kops option in its config (kops get --name $NAME -oyaml):

kubeAPIServer:
  runtimeConfig:
    admissionregistration.k8s.io/v1alpha1: "true"

无论如何，所有组件都可以通过API服务器运行，有时基于配置有时会尝试调用某些禁用功能也就不足为奇了.至少它必须检查支持哪些API，为什么:)

Anyway, all components working thru the API server and it is not a surprise that sometimes based on configuration it is trying to call some disable features. At least it has to check which APIs a supported, so why :)

因此，我认为您无需担心，这是与配置有关的消息.不用担心或者只是启用该功能，它将解决警告消息.

So, I think you don't need to worry about it, that is the configuration-related message. Don't worry about it. Or just enable that feature, it will solve warning messages.

这篇关于Kubernetes 1.8.10 kube-apiserver优先级错误的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！

kOps