You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
kubectl apply -f deploy/
kubectl get deployment/scheduler-framework-sample
NAME READY UP-TO-DATE AVAILABLE AGE
scheduler-framework-sample 0/1 0 0 24s
kubectl get pods -n sw
NAME READY STATUS RESTARTS AGE
pending-example-7c7b8b5658-bh2h8 0/1 Pending 0 7m53s
pending-example-7c7b8b5658-lgj7q 0/1 Pending 0 7m53s
Could you please provide more detailed logs in the pod of deployment/scheduler-framework-sample?
The following is just my guess:
I guess the problem is the version mismatch of Kubernetes and KubeSchedulerConfiguration resource. You can edit the configMap of deployment.yamlhere before applying it.
According to the Kubernetes documentation, Kubernetes v1.21 (My test environment) needs to use the kubescheduler.config.k8s.io/v1beta1 as the apiVersion. However Kubernetes 1.23 and 1.24 need to use v1beta2 or v1beta3, and Kubernetes 1.25 needs to use v1.
Steps to reproduce
CC @FFFFFaraway
The text was updated successfully, but these errors were encountered: