Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Scheduler is never ready so pods are never scheduled #1

Open
husky-parul opened this issue Sep 1, 2022 · 1 comment
Open

Scheduler is never ready so pods are never scheduled #1

husky-parul opened this issue Sep 1, 2022 · 1 comment

Comments

@husky-parul
Copy link

husky-parul commented Sep 1, 2022

Steps to reproduce

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

CC @FFFFFaraway

@FFFFFaraway
Copy link
Owner

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.yaml here 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants