kubernetes / kubernetes

Production-Grade Container Scheduling and Management

Home Page:https://kubernetes.io

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

集群升级kubelet版本高于kube-apiserver版本

Xiaolei1091058519 opened this issue · comments

What happened?

集群版本是1.22.5-00版本,我这边将节点kubelet版本升级到1.23.17-00版本,按照官方文档中的说明,kubelet版本不能高与kube-apiserver版本(1.22.5-00),可是我的节点还是正常可以创建pod资源。节点kubelet日志无异常。目前不确定这样问题出在哪儿,哪位大神可以帮我解答一下。
image
官方文档地址:https://kubernetes.io/zh-cn/releases/version-skew-policy/

What did you expect to happen?

kubelet版本高于kube-apiserver版本,会出现节点notready或者是创建pod资源失败的情况。

How can we reproduce it (as minimally and precisely as possible)?

集群是1.22.5-00版本,其中一个node节点kubelet升级到1.23.17-00版本。

Anything else we need to know?

No response

Kubernetes version

$ kubectl version
#Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.5", GitCommit:"5c99e2ac2ff9a3c549d9ca665e7bc05a3e18f07e", GitTreeState:"clean", BuildDate:"2021-12-16T08:38:33Z", GoVersion:"go1.16.12", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.0", GitCommit:"c2b5237ccd9c0f1d600d3072634ca66cefdf272f", GitTreeState:"clean", BuildDate:"2021-08-04T17:57:25Z", GoVersion:"go1.16.6", Compiler:"gc", Platform:"linux/amd64"}

Cloud provider

none

OS version

# On Linux:
$ cat /etc/os-release
#NAME="Ubuntu"
VERSION="20.04 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal

$ uname -a
#Linux sz-exa-cpu-2 5.4.0-105-generic #119-Ubuntu SMP Mon Mar 7 18:49:24 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux


# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here

Install tools

kubeadm

Container runtime (CRI) and version (if applicable)

docker 24.0.5

Related plugins (CNI, CSI, ...) and versions (if applicable)

There are no sig labels on this issue. Please add an appropriate label by using one of the following commands:

  • /sig <group-name>
  • /wg <group-name>
  • /committee <group-name>

Please see the group list for a listing of the SIGs, working groups, and committees available.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

commented

/kind support
/remove-kind bug

@Xiaolei1091058519
Can you please describe the issue in primary language(English)?

@T-Lakshmi The cluster version is version 1.22.5-00. Upgrade the kubelet version of one of the nodes to version 1.23.17-00. According to the instructions in the official documentation, the kubelet version(1.23.17-00) cannot be higher than the kube-apiserver version (1.22.5-00). But currently my node can create pod resources normally. There are no exceptions in the node kubelet logs.

github issue is not the right place for support requests.

You can post your question on the Kubernetes Slack or the Discuss Kubernetes forum.

/close

@HirazawaUi: Closing this issue.

In response to this:

github issue is not the right place for support requests.

You can post your question on the Kubernetes Slack or the Discuss Kubernetes forum.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.