I0401 16:24:50.497829       1 serving.go:348] Generated self-signed cert in-memory
I0401 16:24:55.454819       1 server.go:154] "Starting Kubernetes Scheduler" version="v1.28.13"
I0401 16:24:55.454844       1 server.go:156] "Golang settings" GOGC="" GOMAXPROCS="" GOTRACEBACK=""
I0401 16:25:39.361759       1 requestheader_controller.go:169] Starting RequestHeaderAuthRequestController
I0401 16:25:39.361811       1 shared_informer.go:311] Waiting for caches to sync for RequestHeaderAuthRequestController
I0401 16:25:39.361864       1 configmap_cafile_content.go:202] "Starting controller" name="client-ca::kube-system::extension-apiserver-authentication::client-ca-file"
I0401 16:25:39.361892       1 shared_informer.go:311] Waiting for caches to sync for client-ca::kube-system::extension-apiserver-authentication::client-ca-file
I0401 16:25:39.361894       1 secure_serving.go:213] Serving securely on [::]:10259
I0401 16:25:39.361980       1 tlsconfig.go:240] "Starting DynamicServingCertificateController"
I0401 16:25:39.361980       1 configmap_cafile_content.go:202] "Starting controller" name="client-ca::kube-system::extension-apiserver-authentication::requestheader-client-ca-file"
I0401 16:25:39.366598       1 shared_informer.go:311] Waiting for caches to sync for client-ca::kube-system::extension-apiserver-authentication::requestheader-client-ca-file
I0401 16:25:39.462486       1 shared_informer.go:318] Caches are synced for client-ca::kube-system::extension-apiserver-authentication::client-ca-file
I0401 16:25:39.462584       1 shared_informer.go:318] Caches are synced for RequestHeaderAuthRequestController
I0401 16:25:39.462662       1 leaderelection.go:250] attempting to acquire leader lease kube-system/kube-scheduler...
I0401 16:25:39.467213       1 shared_informer.go:318] Caches are synced for client-ca::kube-system::extension-apiserver-authentication::requestheader-client-ca-file
E0401 16:25:44.463128       1 leaderelection.go:332] error retrieving resource lock kube-system/kube-scheduler: Get "https://199.204.45.102:6443/apis/coordination.k8s.io/v1/namespaces/kube-system/leases/kube-scheduler?timeout=5s": net/http: request canceled (Client.Timeout exceeded while awaiting headers)
E0401 16:25:46.331940       1 webhook.go:154] Failed to make webhook authenticator request: Post "https://199.204.45.102:6443/apis/authentication.k8s.io/v1/tokenreviews": dial tcp 199.204.45.102:6443: connect: connection refused
E0401 16:25:46.332071       1 authentication.go:73] "Unable to authenticate the request" err="[invalid bearer token, Post \"https://199.204.45.102:6443/apis/authentication.k8s.io/v1/tokenreviews\": dial tcp 199.204.45.102:6443: connect: connection refused]"
E0401 16:25:47.358796       1 leaderelection.go:332] error retrieving resource lock kube-system/kube-scheduler: Get "https://199.204.45.102:6443/apis/coordination.k8s.io/v1/namespaces/kube-system/leases/kube-scheduler?timeout=5s": dial tcp 199.204.45.102:6443: connect: connection refused
E0401 16:25:51.301850       1 leaderelection.go:332] error retrieving resource lock kube-system/kube-scheduler: Get "https://199.204.45.102:6443/apis/coordination.k8s.io/v1/namespaces/kube-system/leases/kube-scheduler?timeout=5s": dial tcp 199.204.45.102:6443: connect: connection refused
E0401 16:25:54.955057       1 leaderelection.go:332] error retrieving resource lock kube-system/kube-scheduler: Get "https://199.204.45.102:6443/apis/coordination.k8s.io/v1/namespaces/kube-system/leases/kube-scheduler?timeout=5s": dial tcp 199.204.45.102:6443: connect: connection refused
E0401 16:25:57.169129       1 leaderelection.go:332] error retrieving resource lock kube-system/kube-scheduler: Get "https://199.204.45.102:6443/apis/coordination.k8s.io/v1/namespaces/kube-system/leases/kube-scheduler?timeout=5s": dial tcp 199.204.45.102:6443: connect: connection refused
E0401 16:26:01.183829       1 leaderelection.go:332] error retrieving resource lock kube-system/kube-scheduler: Get "https://199.204.45.102:6443/apis/coordination.k8s.io/v1/namespaces/kube-system/leases/kube-scheduler?timeout=5s": dial tcp 199.204.45.102:6443: connect: connection refused
E0401 16:26:04.053480       1 leaderelection.go:332] error retrieving resource lock kube-system/kube-scheduler: Get "https://199.204.45.102:6443/apis/coordination.k8s.io/v1/namespaces/kube-system/leases/kube-scheduler?timeout=5s": dial tcp 199.204.45.102:6443: connect: connection refused
E0401 16:26:08.051385       1 leaderelection.go:332] error retrieving resource lock kube-system/kube-scheduler: Get "https://199.204.45.102:6443/apis/coordination.k8s.io/v1/namespaces/kube-system/leases/kube-scheduler?timeout=5s": dial tcp 199.204.45.102:6443: connect: connection refused
E0401 16:26:12.120274       1 leaderelection.go:332] error retrieving resource lock kube-system/kube-scheduler: Get "https://199.204.45.102:6443/apis/coordination.k8s.io/v1/namespaces/kube-system/leases/kube-scheduler?timeout=5s": dial tcp 199.204.45.102:6443: connect: connection refused
E0401 16:26:15.706222       1 leaderelection.go:332] error retrieving resource lock kube-system/kube-scheduler: Get "https://199.204.45.102:6443/apis/coordination.k8s.io/v1/namespaces/kube-system/leases/kube-scheduler?timeout=5s": dial tcp 199.204.45.102:6443: connect: connection refused
E0401 16:26:16.325587       1 webhook.go:154] Failed to make webhook authenticator request: Post "https://199.204.45.102:6443/apis/authentication.k8s.io/v1/tokenreviews": dial tcp 199.204.45.102:6443: connect: connection refused
E0401 16:26:16.325725       1 authentication.go:73] "Unable to authenticate the request" err="[invalid bearer token, Post \"https://199.204.45.102:6443/apis/authentication.k8s.io/v1/tokenreviews\": dial tcp 199.204.45.102:6443: connect: connection refused]"
E0401 16:26:19.048555       1 leaderelection.go:332] error retrieving resource lock kube-system/kube-scheduler: Get "https://199.204.45.102:6443/apis/coordination.k8s.io/v1/namespaces/kube-system/leases/kube-scheduler?timeout=5s": dial tcp 199.204.45.102:6443: connect: connection refused
E0401 16:26:22.758908       1 leaderelection.go:332] error retrieving resource lock kube-system/kube-scheduler: Get "https://199.204.45.102:6443/apis/coordination.k8s.io/v1/namespaces/kube-system/leases/kube-scheduler?timeout=5s": dial tcp 199.204.45.102:6443: connect: connection refused
E0401 16:26:25.727218       1 leaderelection.go:332] error retrieving resource lock kube-system/kube-scheduler: Get "https://199.204.45.102:6443/apis/coordination.k8s.io/v1/namespaces/kube-system/leases/kube-scheduler?timeout=5s": dial tcp 199.204.45.102:6443: connect: connection refused
E0401 16:26:29.843813       1 leaderelection.go:332] error retrieving resource lock kube-system/kube-scheduler: Get "https://199.204.45.102:6443/apis/coordination.k8s.io/v1/namespaces/kube-system/leases/kube-scheduler?timeout=5s": dial tcp 199.204.45.102:6443: connect: connection refused
E0401 16:26:33.924887       1 leaderelection.go:332] error retrieving resource lock kube-system/kube-scheduler: Get "https://199.204.45.102:6443/apis/coordination.k8s.io/v1/namespaces/kube-system/leases/kube-scheduler?timeout=5s": dial tcp 199.204.45.102:6443: connect: connection refused
E0401 16:26:36.456877       1 leaderelection.go:332] error retrieving resource lock kube-system/kube-scheduler: Get "https://199.204.45.102:6443/apis/coordination.k8s.io/v1/namespaces/kube-system/leases/kube-scheduler?timeout=5s": dial tcp 199.204.45.102:6443: connect: connection refused
E0401 16:26:38.600142       1 leaderelection.go:332] error retrieving resource lock kube-system/kube-scheduler: Get "https://199.204.45.102:6443/apis/coordination.k8s.io/v1/namespaces/kube-system/leases/kube-scheduler?timeout=5s": dial tcp 199.204.45.102:6443: connect: connection refused
E0401 16:26:41.606268       1 leaderelection.go:332] error retrieving resource lock kube-system/kube-scheduler: Get "https://199.204.45.102:6443/apis/coordination.k8s.io/v1/namespaces/kube-system/leases/kube-scheduler?timeout=5s": dial tcp 199.204.45.102:6443: connect: connection refused
E0401 16:26:44.516479       1 leaderelection.go:332] error retrieving resource lock kube-system/kube-scheduler: Get "https://199.204.45.102:6443/apis/coordination.k8s.io/v1/namespaces/kube-system/leases/kube-scheduler?timeout=5s": dial tcp 199.204.45.102:6443: connect: connection refused
E0401 16:26:46.325149       1 webhook.go:154] Failed to make webhook authenticator request: Post "https://199.204.45.102:6443/apis/authentication.k8s.io/v1/tokenreviews": dial tcp 199.204.45.102:6443: connect: connection refused
E0401 16:26:46.325338       1 authentication.go:73] "Unable to authenticate the request" err="[invalid bearer token, Post \"https://199.204.45.102:6443/apis/authentication.k8s.io/v1/tokenreviews\": dial tcp 199.204.45.102:6443: connect: connection refused]"
E0401 16:26:47.865954       1 leaderelection.go:332] error retrieving resource lock kube-system/kube-scheduler: Get "https://199.204.45.102:6443/apis/coordination.k8s.io/v1/namespaces/kube-system/leases/kube-scheduler?timeout=5s": dial tcp 199.204.45.102:6443: connect: connection refused
E0401 16:26:50.889434       1 leaderelection.go:332] error retrieving resource lock kube-system/kube-scheduler: Get "https://199.204.45.102:6443/apis/coordination.k8s.io/v1/namespaces/kube-system/leases/kube-scheduler?timeout=5s": dial tcp 199.204.45.102:6443: connect: connection refused
E0401 16:26:53.615032       1 leaderelection.go:332] error retrieving resource lock kube-system/kube-scheduler: Get "https://199.204.45.102:6443/apis/coordination.k8s.io/v1/namespaces/kube-system/leases/kube-scheduler?timeout=5s": dial tcp 199.204.45.102:6443: connect: connection refused
E0401 16:26:56.915484       1 leaderelection.go:332] error retrieving resource lock kube-system/kube-scheduler: Get "https://199.204.45.102:6443/apis/coordination.k8s.io/v1/namespaces/kube-system/leases/kube-scheduler?timeout=5s": dial tcp 199.204.45.102:6443: connect: connection refused
E0401 16:27:00.074275       1 leaderelection.go:332] error retrieving resource lock kube-system/kube-scheduler: Get "https://199.204.45.102:6443/apis/coordination.k8s.io/v1/namespaces/kube-system/leases/kube-scheduler?timeout=5s": dial tcp 199.204.45.102:6443: connect: connection refused
E0401 16:27:02.541201       1 leaderelection.go:332] error retrieving resource lock kube-system/kube-scheduler: Get "https://199.204.45.102:6443/apis/coordination.k8s.io/v1/namespaces/kube-system/leases/kube-scheduler?timeout=5s": dial tcp 199.204.45.102:6443: connect: connection refused
E0401 16:27:06.332092       1 leaderelection.go:332] error retrieving resource lock kube-system/kube-scheduler: Get "https://199.204.45.102:6443/apis/coordination.k8s.io/v1/namespaces/kube-system/leases/kube-scheduler?timeout=5s": dial tcp 199.204.45.102:6443: connect: connection refused
E0401 16:27:08.981990       1 leaderelection.go:332] error retrieving resource lock kube-system/kube-scheduler: Get "https://199.204.45.102:6443/apis/coordination.k8s.io/v1/namespaces/kube-system/leases/kube-scheduler?timeout=5s": dial tcp 199.204.45.102:6443: connect: connection refused
E0401 16:27:11.032831       1 leaderelection.go:332] error retrieving resource lock kube-system/kube-scheduler: Get "https://199.204.45.102:6443/apis/coordination.k8s.io/v1/namespaces/kube-system/leases/kube-scheduler?timeout=5s": dial tcp 199.204.45.102:6443: connect: connection refused
E0401 16:27:14.629167       1 leaderelection.go:332] error retrieving resource lock kube-system/kube-scheduler: Get "https://199.204.45.102:6443/apis/coordination.k8s.io/v1/namespaces/kube-system/leases/kube-scheduler?timeout=5s": dial tcp 199.204.45.102:6443: connect: connection refused
E0401 16:27:16.325444       1 webhook.go:154] Failed to make webhook authenticator request: Post "https://199.204.45.102:6443/apis/authentication.k8s.io/v1/tokenreviews": dial tcp 199.204.45.102:6443: connect: connection refused
E0401 16:27:16.325558       1 authentication.go:73] "Unable to authenticate the request" err="[invalid bearer token, Post \"https://199.204.45.102:6443/apis/authentication.k8s.io/v1/tokenreviews\": dial tcp 199.204.45.102:6443: connect: connection refused]"
E0401 16:27:17.422034       1 leaderelection.go:332] error retrieving resource lock kube-system/kube-scheduler: Get "https://199.204.45.102:6443/apis/coordination.k8s.io/v1/namespaces/kube-system/leases/kube-scheduler?timeout=5s": dial tcp 199.204.45.102:6443: connect: connection refused
E0401 16:27:19.639258       1 leaderelection.go:332] error retrieving resource lock kube-system/kube-scheduler: Get "https://199.204.45.102:6443/apis/coordination.k8s.io/v1/namespaces/kube-system/leases/kube-scheduler?timeout=5s": dial tcp 199.204.45.102:6443: connect: connection refused
E0401 16:27:22.577761       1 leaderelection.go:332] error retrieving resource lock kube-system/kube-scheduler: Get "https://199.204.45.102:6443/apis/coordination.k8s.io/v1/namespaces/kube-system/leases/kube-scheduler?timeout=5s": dial tcp 199.204.45.102:6443: connect: connection refused
E0401 16:27:26.931155       1 leaderelection.go:332] error retrieving resource lock kube-system/kube-scheduler: Get "https://199.204.45.102:6443/apis/coordination.k8s.io/v1/namespaces/kube-system/leases/kube-scheduler?timeout=5s": dial tcp 199.204.45.102:6443: connect: connection refused
E0401 16:27:29.512572       1 leaderelection.go:332] error retrieving resource lock kube-system/kube-scheduler: Get "https://199.204.45.102:6443/apis/coordination.k8s.io/v1/namespaces/kube-system/leases/kube-scheduler?timeout=5s": dial tcp 199.204.45.102:6443: connect: connection refused
E0401 16:27:32.641181       1 leaderelection.go:332] error retrieving resource lock kube-system/kube-scheduler: Get "https://199.204.45.102:6443/apis/coordination.k8s.io/v1/namespaces/kube-system/leases/kube-scheduler?timeout=5s": dial tcp 199.204.45.102:6443: connect: connection refused
E0401 16:27:37.725464       1 leaderelection.go:332] error retrieving resource lock kube-system/kube-scheduler: leases.coordination.k8s.io "kube-scheduler" is forbidden: User "system:kube-scheduler" cannot get resource "leases" in API group "coordination.k8s.io" in the namespace "kube-system"
E0401 16:27:37.725573       1 reflector.go:147] k8s.io/client-go@v0.0.0/tools/cache/reflector.go:229: Failed to watch *v1.Namespace: unknown (get namespaces)
I0401 16:27:40.154884       1 leaderelection.go:260] successfully acquired lease kube-system/kube-scheduler
E0401 16:39:45.712518       1 leaderelection.go:332] error retrieving resource lock kube-system/kube-scheduler: Get "https://199.204.45.102:6443/apis/coordination.k8s.io/v1/namespaces/kube-system/leases/kube-scheduler?timeout=5s": net/http: request canceled (Client.Timeout exceeded while awaiting headers)
E0401 16:39:50.711492       1 leaderelection.go:369] Failed to update lock: Put "https://199.204.45.102:6443/apis/coordination.k8s.io/v1/namespaces/kube-system/leases/kube-scheduler?timeout=5s": context deadline exceeded
I0401 16:39:50.711550       1 leaderelection.go:285] failed to renew lease kube-system/kube-scheduler: timed out waiting for the condition
E0401 16:39:51.857185       1 leaderelection.go:308] Failed to release lock: Operation cannot be fulfilled on leases.coordination.k8s.io "kube-scheduler": the object has been modified; please apply your changes to the latest version and try again
E0401 16:39:51.857228       1 server.go:242] "Leaderelection lost"