scheduler-plugins icon indicating copy to clipboard operation
scheduler-plugins copied to clipboard
verified publisher icon kubernetes-sigs

kube-scheduler failed to start with k8s v1.24.2

Open riyazhakki opened this issue 3 years ago • 2 comments

My k8s version is v1.24.2, compiled my scheduler-plugins at master.

while starting the kube-scheduler container throwing following error.

$ kubectl logs pod/kube-scheduler-c7-master-vm2 -n kube-system Flag --port has been deprecated, This flag has no effect now and will be removed in v1.24. You can use --secure-port instead. I0627 15:15:46.623770 1 serving.go:348] Generated self-signed cert in-memory E0627 15:15:46.624607 1 run.go:74] "command failed" err="no kind "KubeSchedulerConfiguration" is registered for version "kubescheduler.config.k8s.io/v1beta1" in scheme "k8s.io/kubernetes/pkg/scheduler/apis/config/scheme/scheme.go:30""

riyazhakki avatar Jun 28 '22 02:06 riyazhakki

@riyazhakki given the master branch is still at 1.23, that behavior is as expected:

https://github.com/kubernetes-sigs/scheduler-plugins/blob/1550aa8419628b7d0520ee594fec7718444426d4/go.mod#L24

We will soon cut an official 1.23 image, along with bumping master to 1.24.

@fromanirh @Tal-or please let me know which ongoing PRs are disired to be merged before we bump to 1.24.

Huang-Wei avatar Jun 28 '22 17:06 Huang-Wei

Hi @Huang-Wei , we have:

  • https://github.com/kubernetes-sigs/scheduler-plugins/pull/377 - which I'll review again ASAP and
  • https://github.com/kubernetes-sigs/scheduler-plugins/pull/372 - which is ready for review everything else (namely https://github.com/kubernetes-sigs/scheduler-plugins/pull/315) can wait

ffromani avatar Jun 28 '22 17:06 ffromani

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar Sep 27 '22 06:09 k8s-triage-robot

/close

Duplicated with #430.

Huang-Wei avatar Sep 27 '22 16:09 Huang-Wei

@Huang-Wei: Closing this issue.

In response to this:

/close

Duplicated with #430.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

k8s-ci-robot avatar Sep 27 '22 16:09 k8s-ci-robot

My k8s version is v1.24.2, compiled my scheduler-plugins at master.

while starting the kube-scheduler container throwing following error.

$ kubectl logs pod/kube-scheduler-c7-master-vm2 -n kube-system Flag --port has been deprecated, This flag has no effect now and will be removed in v1.24. You can use --secure-port instead. I0627 15:15:46.623770 1 serving.go:348] Generated self-signed cert in-memory E0627 15:15:46.624607 1 run.go:74] "command failed" err="no kind "KubeSchedulerConfiguration" is registered for version "kubescheduler.config.k8s.io/v1beta1" in scheme "k8s.io/kubernetes/pkg/scheduler/apis/config/scheme/scheme.go:30""

@riyazhakki Can you please show me your code,as I do not how to start to write a custom one.

zffocussss avatar Oct 11 '22 08:10 zffocussss

@zffocussss you should use at least v1beta2 (which is also deprecated though) in v1.24 - v1beta1 has been removed entirely in v1.24.

Huang-Wei avatar Oct 12 '22 22:10 Huang-Wei