Hi,
I setup a single node cluster using
minikube start --driver=none on a proxmox VM. I deploy my own custom schdeuler and now I am facing error when I run
logs of custom scheduler.
Can anyone guide me in this regard? I also configure the RBAC files and everything, but could not know the issue. My idea is may be minikube have some issues when running on VM or using VM as node?
kubectl logs my-scheduler-5b9764786f-smrlk -n kube-system
I0502 11:57:22.274558 1 registry.go:173] Registering SelectorSpread plugin
I0502 11:57:22.274611 1 registry.go:173] Registering SelectorSpread plugin
I0502 11:57:22.529008 1 serving.go:331] Generated self-signed cert in-memory
W0502 11:57:22.665600 1 options.go:332] Neither --kubeconfig nor --master was specified. Using default API client. This might not work.
I0502 11:57:22.673697 1 registry.go:173] Registering SelectorSpread plugin
I0502 11:57:22.673717 1 registry.go:173] Registering SelectorSpread plugin
W0502 11:57:22.676335 1 authorization.go:47] Authorization is disabled
W0502 11:57:22.676535 1 authentication.go:40] Authentication is disabled
I0502 11:57:22.676587 1 deprecated_insecure_serving.go:51] Serving healthz insecurely on [::]:10251
I0502 11:57:22.680372 1 requestheader_controller.go:169] Starting RequestHeaderAuthRequestController
I0502 11:57:22.680404 1 configmap_cafile_content.go:202] Starting client-ca::kube-system::extension-apiserver-authentication::client-ca-file
I0502 11:57:22.680404 1 configmap_cafile_content.go:202] Starting client-ca::kube-system::extension-apiserver-authentication::requestheader-client-ca-file
I0502 11:57:22.680439 1 shared_informer.go:240] Waiting for caches to sync for client-ca::kube-system::extension-apiserver-authentication::client-ca-file
I0502 11:57:22.680535 1 shared_informer.go:240] Waiting for caches to sync for client-ca::kube-system::extension-apiserver-authentication::requestheader-client-ca-file
I0502 11:57:22.680626 1 secure_serving.go:197] Serving securely on [::]:10259
I0502 11:57:22.680431 1 shared_informer.go:240] Waiting for caches to sync for RequestHeaderAuthRequestController
I0502 11:57:22.680690 1 tlsconfig.go:240] Starting DynamicServingCertificateController
E0502 11:57:22.684264 1 reflector.go:127] k8s.io/client-go/informers/factory.go:134: Failed to watch *v1beta1.PodDisruptionBudget: failed to list *v1beta1.PodDisruptionBudget: the server could not find the requested resource
I0502 11:57:22.780688 1 shared_informer.go:247] Caches are synced for client-ca::kube-system::extension-apiserver-authentication::requestheader-client-ca-file
I0502 11:57:22.780717 1 shared_informer.go:247] Caches are synced for client-ca::kube-system::extension-apiserver-authentication::client-ca-file
I0502 11:57:22.780882 1 shared_informer.go:247] Caches are synced for RequestHeaderAuthRequestController
E0502 11:57:23.890677 1 reflector.go:127] k8s.io/client-go/informers/factory.go:134: Failed to watch *v1beta1.PodDisruptionBudget: failed to list *v1beta1.PodDisruptionBudget: the server could not find the requested resource
E0502 11:57:25.750531 1 reflector.go:127] k8s.io/client-go/informers/factory.go:134: Failed to watch *v1beta1.PodDisruptionBudget: failed to list *v1beta1.PodDisruptionBudget: the server could not find the requested resource
E0502 11:57:31.943421 1 reflector.go:127] k8s.io/client-go/informers/factory.go:134: Failed to watch *v1beta1.PodDisruptionBudget: failed to list *v1beta1.PodDisruptionBudget: the server could not find the requested resource
E0502 11:57:42.920555 1 reflector.go:127] k8s.io/client-go/informers/factory.go:134: Failed to watch *v1beta1.PodDisruptionBudget: failed to list *v1beta1.PodDisruptionBudget: the server could not find the requested resource
E0502 11:57:56.333262 1 reflector.go:127] k8s.io/client-go/informers/factory.go:134: Failed to watch *v1beta1.PodDisruptionBudget: failed to list *v1beta1.PodDisruptionBudget: the server could not find the requested resource
E0502 11:58:43.861629 1 reflector.go:127] k8s.io/client-go/informers/factory.go:134: Failed to watch *v1beta1.PodDisruptionBudget: failed to list *v1beta1.PodDisruptionBudget: the server could not find the requested resource
For log of default kube-scheduler
kubectl logs kube-scheduler-ubuntu22.04lts -n kube-systemI0502 11:57:18.592624 1 serving.go:348] Generated self-signed cert in-memory
W0502 11:57:20.597068 1 requestheader_controller.go:193] 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'
W0502 11:57:20.597173 1 authentication.go:368] 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"
W0502 11:57:20.597198 1 authentication.go:369] Continuing without authentication configuration. This may treat all requests as anonymous.
W0502 11:57:20.597238 1 authentication.go:370] To require authentication configuration lookup to succeed, set --authentication-tolerate-lookup-failure=false
I0502 11:57:20.630860 1 server.go:154] "Starting Kubernetes Scheduler" version="v1.28.3"
I0502 11:57:20.630889 1 server.go:156] "Golang settings" GOGC="" GOMAXPROCS="" GOTRACEBACK=""
I0502 11:57:20.631909 1 configmap_cafile_content.go:202] "Starting controller" name="client-ca::kube-system::extension-apiserver-authentication::client-ca-file"
I0502 11:57:20.631966 1 shared_informer.go:311] Waiting for caches to sync for client-ca::kube-system::extension-apiserver-authentication::client-ca-file
I0502 11:57:20.632405 1 secure_serving.go:213] Serving securely on 127.0.0.1:10259
I0502 11:57:20.632591 1 tlsconfig.go:240] "Starting DynamicServingCertificateController"
I0502 11:57:20.732164 1 shared_informer.go:318] Caches are synced for client-ca::kube-system::extension-apiserver-authentication::client-ca-file