Kubernetes 1.8.10 kube-apiserver priorityclasses 错误
Kubernetes 1.8.10 kube-apiserver priorityclasses error
使用 kops 旋转的新集群 1.8.10。
K8S 1.8 有一个新特性Pod Priority and Preemption
。
更多信息: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
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)。
没有 pod 在使用 priorityClassName
。
运行说明:
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
特有的?
我认为这与其配置中的 Kops 选项有关 (kops get --name $NAME -oyaml
):
kubeAPIServer:
runtimeConfig:
admissionregistration.k8s.io/v1alpha1: "true"
无论如何,所有组件都通过 API 服务器工作,有时根据配置它会尝试调用一些禁用功能并不奇怪。至少它必须检查支持哪个 API,所以为什么 :)
所以,我认为您不必担心,那就是 configuration-related 消息。别担心。或者只启用该功能,它将解决警告消息。
使用 kops 旋转的新集群 1.8.10。
K8S 1.8 有一个新特性Pod Priority and Preemption
。
更多信息: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 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)。
没有 pod 在使用 priorityClassName
。
运行说明:
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
特有的?
我认为这与其配置中的 Kops 选项有关 (kops get --name $NAME -oyaml
):
kubeAPIServer:
runtimeConfig:
admissionregistration.k8s.io/v1alpha1: "true"
无论如何,所有组件都通过 API 服务器工作,有时根据配置它会尝试调用一些禁用功能并不奇怪。至少它必须检查支持哪个 API,所以为什么 :)
所以,我认为您不必担心,那就是 configuration-related 消息。别担心。或者只启用该功能,它将解决警告消息。