Kubernetes 1.8.10 kube-apiserver优先级错误 [英] Kubernetes 1.8.10 kube-apiserver priorityclasses error

问题描述

新的集群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记录错误

I0321 16:27:50.922589 7 wrap.go:42] GET /apis/admissionregistration.k8s.io/v1alpha1/initializerconfigurations: (140.067µs)404 [[kube-apiserver/v1.8.10(linux/amd64) kubernetes/044cd26] 127.0.0.1:47500] I0321 16:27:51.257756 7 wrap.go:42] GET /apis/scheduling.k8s.io/v1alpha1/priorityclasses?resourceVersion=0: (168.391µs)404 [[kube-apiserver/v1.8.10(linux/amd64) kubernetes/044cd26] 127.0.0.1:47500] E0321 16:27:51.258176 7 mirror.go:205] k8s.io/kubernetes/pkg/client/informers/informers_produced/internalversion/factory.go:73: 无法列出* scheduling.PriorityClass:服务器找不到 请求的资源(获取优先级class.scheduling.k8s.io)

I0321 16:27:50.922589 7 wrap.go:42] GET /apis/admissionregistration.k8s.io/v1alpha1/initializerconfigurations: (140.067µs) 404 [[kube-apiserver/v1.8.10 (linux/amd64) kubernetes/044cd26] 127.0.0.1:47500] I0321 16:27:51.257756 7 wrap.go:42] GET /apis/scheduling.k8s.io/v1alpha1/priorityclasses?resourceVersion=0: (168.391µs) 404 [[kube-apiserver/v1.8.10 (linux/amd64) kubernetes/044cd26] 127.0.0.1:47500] E0321 16:27:51.258176 7 reflector.go:205] k8s.io/kubernetes/pkg/client/informers/informers_generated/internalversion/factory.go:73: Failed to list *scheduling.PriorityClass: the server could not find the requested resource (get priorityclasses.scheduling.k8s.io)

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

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

没有吊舱正在使用priorityClassName.

运行说明:

kubectl解释priorityclass错误:API版本: 服务器不支持Scheduling.k8s.io/v1alpha1.使用以下之一: [apiregistration.k8s.io/v1beta1扩展程序/v1beta1应用程序/v1beta1 apps/v1beta2 authentication.k8s.io/v1
authentication.k8s.io/v1beta1授权.k8s.io/v1 authorization.k8s.io/v1beta1自动缩放/v1自动缩放/v2beta1 批处理/v1批处理/v1beta1证书.k8s.io/v1beta1 network.k8s.io/v1策略/v1beta1 rbac.authorization.k8s.io/v1 rbac.authorization.k8s.io/v1beta1 storage.k8s.io/v1 storage.k8s.io/v1beta1 apiextensions.k8s.io/v1beta1 v1]

kubectl explain priorityclass error: API version: scheduling.k8s.io/v1alpha1 is not supported by the server. Use one of: [apiregistration.k8s.io/v1beta1 extensions/v1beta1 apps/v1beta1 apps/v1beta2 authentication.k8s.io/v1
authentication.k8s.io/v1beta1 authorization.k8s.io/v1 authorization.k8s.io/v1beta1 autoscaling/v1 autoscaling/v2beta1 batch/v1 batch/v1beta1 certificates.k8s.io/v1beta1 networking.k8s.io/v1 policy/ v1beta1 rbac.authorization.k8s.io/v1 rbac.authorization.k8s.io/v1beta1 storage.k8s.io/v1 storage.k8s.io/v1beta1 apiextensions.k8s.io/v1beta1 v1]

这是正常的还是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优先级错误的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！