I0617 19:04:53.579472 1 serving.go:386] Generated self-signed cert in-memory W0617 19:04:54.686255 1 requestheader_controller.go:204] Unable to get configmap/extension-apiserver-authentication in kube-system. Usually fixed by 'kubectl create rolebinding -n kube-system ROLEBINDING_NAME --role=extension-apiserver-authentication-reader --serviceaccount=YOUR_NS:YOUR_SA' W0617 19:04:54.686288 1 authentication.go:397] Error looking up in-cluster authentication configuration: configmaps "extension-apiserver-authentication" is forbidden: User "system:kube-scheduler" cannot get resource "configmaps" in API group "" in the namespace "kube-system" W0617 19:04:54.686296 1 authentication.go:398] Continuing without authentication configuration. This may treat all requests as anonymous. W0617 19:04:54.686303 1 authentication.go:399] To require authentication configuration lookup to succeed, set --authentication-tolerate-lookup-failure=false I0617 19:04:54.705940 1 server.go:171] "Starting Kubernetes Scheduler" version="v1.33.4" I0617 19:04:54.705985 1 server.go:173] "Golang settings" GOGC="" GOMAXPROCS="" GOTRACEBACK="" I0617 19:04:54.709832 1 configmap_cafile_content.go:205] "Starting controller" name="client-ca::kube-system::extension-apiserver-authentication::client-ca-file" I0617 19:04:54.709870 1 shared_informer.go:350] "Waiting for caches to sync" controller="client-ca::kube-system::extension-apiserver-authentication::client-ca-file" I0617 19:04:54.710606 1 secure_serving.go:211] Serving securely on [::]:10259 I0617 19:04:54.710875 1 tlsconfig.go:243] "Starting DynamicServingCertificateController" I0617 19:04:54.810315 1 shared_informer.go:357] "Caches are synced" controller="client-ca::kube-system::extension-apiserver-authentication::client-ca-file" I0617 19:04:54.811349 1 leaderelection.go:257] attempting to acquire leader lease kube-system/kube-scheduler... E0617 19:06:37.305407 1 leaderelection.go:436] error retrieving resource lock kube-system/kube-scheduler: the server was unable to return a response in the time allotted, but may still be processing the request (get leases.coordination.k8s.io kube-scheduler) E0617 19:06:45.525988 1 leaderelection.go:436] error retrieving resource lock kube-system/kube-scheduler: Get "https://199.204.45.223:6443/apis/coordination.k8s.io/v1/namespaces/kube-system/leases/kube-scheduler?timeout=5s": net/http: request canceled (Client.Timeout exceeded while awaiting headers) E0617 19:06:53.080188 1 leaderelection.go:436] error retrieving resource lock kube-system/kube-scheduler: Get "https://199.204.45.223:6443/apis/coordination.k8s.io/v1/namespaces/kube-system/leases/kube-scheduler?timeout=5s": context deadline exceeded E0617 19:07:01.728127 1 leaderelection.go:436] error retrieving resource lock kube-system/kube-scheduler: Get "https://199.204.45.223:6443/apis/coordination.k8s.io/v1/namespaces/kube-system/leases/kube-scheduler?timeout=5s": net/http: request canceled (Client.Timeout exceeded while awaiting headers) E0617 19:07:09.291854 1 leaderelection.go:436] error retrieving resource lock kube-system/kube-scheduler: the server was unable to return a response in the time allotted, but may still be processing the request (get leases.coordination.k8s.io kube-scheduler) E0617 19:07:17.838904 1 leaderelection.go:436] error retrieving resource lock kube-system/kube-scheduler: Get "https://199.204.45.223:6443/apis/coordination.k8s.io/v1/namespaces/kube-system/leases/kube-scheduler?timeout=5s": context deadline exceeded E0617 19:07:26.203899 1 leaderelection.go:436] error retrieving resource lock kube-system/kube-scheduler: Get "https://199.204.45.223:6443/apis/coordination.k8s.io/v1/namespaces/kube-system/leases/kube-scheduler?timeout=5s": context deadline exceeded E0617 19:07:35.166703 1 leaderelection.go:436] error retrieving resource lock kube-system/kube-scheduler: Get "https://199.204.45.223:6443/apis/coordination.k8s.io/v1/namespaces/kube-system/leases/kube-scheduler?timeout=5s": net/http: request canceled (Client.Timeout exceeded while awaiting headers)