kube-scheduler doesn't work properly after reboot #11134
Labels
kind/bug
Categorizes issue or PR as related to a bug.
Comments
|
I have the same error as well |
|
I have the same error too in the same situation. |
|
Would you please run the following commands: |
|
Sure! Here are the outputs: >kubectl get cm extension-apiserver-authentication -n kube-system
NAME DATA AGE
extension-apiserver-authentication 6 25d
>kubectl describe role extension-apiserver-authentication-reader -n kube-system
Name: extension-apiserver-authentication-reader
Labels: [kubernetes.io/bootstrapping=rbac-defaults](http://kubernetes.io/bootstrapping=rbac-defaults)
Annotations: [rbac.authorization.kubernetes.io/autoupdate:](http://rbac.authorization.kubernetes.io/autoupdate:) true
PolicyRule:
Resources Non-Resource URLs Resource Names Verbs
--------- ----------------- -------------- -----
configmaps [] [extension-apiserver-authentication] [get list watch]
> kubectl describe [rolebindings.rbac.authorization.k8s.io](http://rolebindings.rbac.authorization.k8s.io/) system::extension-apiserver-authentication-reader -n kube-system
Name: system::extension-apiserver-authentication-reader
Labels: [kubernetes.io/bootstrapping=rbac-defaults](http://kubernetes.io/bootstrapping=rbac-defaults)
Annotations: [rbac.authorization.kubernetes.io/autoupdate:](http://rbac.authorization.kubernetes.io/autoupdate:) true
Role:
Kind: Role
Name: extension-apiserver-authentication-reader
Subjects:
Kind Name Namespace
---- ---- ---------
User system:kube-controller-manager
User system:kube-scheduler |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened?
I successfully installed a Kubernetes cluster on my RHEL servers. However, kube-scheduler does not work properly after rebooting the master node. It doesn't clean up completed jobs and terminated pods. I installed two different clusters, and both of them have the same issue. kube-scheduler logs show that it cannot access some resources, but system:kube-scheduler looks good to me, though.
kube-scheduler logs
system:kube-scheduler
What did you expect to happen?
kube-scheduler should work properly.
How can we reproduce it (as minimally and precisely as possible)?
git checkout v2.24.1 docker pull quay.io/kubespray/kubespray:v2.24.1 docker run --rm -it -v "(pwd)/inventory:/inventory" quay.io/kubespray/kubespray:v2.24.1 bash ansible-playbook -i /inventory/prod/inventory.ini --diff --become cluster.yml -e kube_version=v1.28.6OS
NAME="Red Hat Enterprise Linux"
VERSION="9.3 (Plow)"
ID="rhel"
ID_LIKE="fedora"
VERSION_ID="9.3"
PLATFORM_ID="platform:el9"
PRETTY_NAME="Red Hat Enterprise Linux 9.3 (Plow)"
ANSI_COLOR="0;31"
LOGO="fedora-logo-icon"
CPE_NAME="cpe:/o:redhat:enterprise_linux:9::baseos"
HOME_URL=https://www.redhat.com/
DOCUMENTATION_URL=https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9
BUG_REPORT_URL=https://bugzilla.redhat.com/
REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 9"
REDHAT_BUGZILLA_PRODUCT_VERSION=9.3
REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="9.3"
Version of Ansible
version in quay.io/kubespray/kubespray:v2.24.1
ansible [core 2.15.8]
config file = /kubespray/ansible.cfg
configured module search path = ['/kubespray/library']
ansible python module location = /usr/local/lib/python3.10/dist-packages/ansible
ansible collection location = /root/.ansible/collections:/usr/share/ansible/collections
executable location = /usr/local/bin/ansible
python version = 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0] (/usr/bin/python3)
jinja version = 3.1.2
libyaml = True
Version of Python
version in quay.io/kubespray/kubespray:v2.24.1
Version of Kubespray (commit)
v2.24.1
Network plugin used
cilium
Full inventory with variables
Command used to invoke ansible
ansible-playbook -i /inventory/prod/inventory.ini --diff --become cluster.yml -e kube_version=v1.28.6
Output of ansible run
Anything else we need to know
No response
The text was updated successfully, but these errors were encountered: