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

stork-scheduler pods crashing after k8s 1.29.4 update #560

Closed
sweepchild opened this issue Apr 23, 2024 · 1 comment
Closed

stork-scheduler pods crashing after k8s 1.29.4 update #560

sweepchild opened this issue Apr 23, 2024 · 1 comment

Comments

@sweepchild
Copy link

sweepchild commented Apr 23, 2024

Is this a BUG REPORT or FEATURE REQUEST?:

BUG REPORT

What happened:

After upgrade k8s-cluster from 1.28.8 to 1.29.4 stork-scheduler pods crashing. When i check logs, saw that:
"command failed" err="no kind \"KubeSchedulerConfiguration\" is registered for version \"kubescheduler.config.k8s.io/v1beta3\" in scheme \"pkg/runtime/scheme.go:100\"

What you expected to happen:

pods will be up and running

How to reproduce it (as minimally and precisely as possible):

Install portworx/portworx (3.1.0) helm chart

Anything else we need to know?:

Also upgraded px 3.0.0 to 3.1.0 before cluster because of 3.0.0 does not support k8s 1.29 (https://docs.portworx.com/portworx-enterprise/install-portworx/prerequisites)

Environment:

  • Container Orchestrator and version:

Kubernetes - v1.29.4 - On-Premise

  • Cloud provider or hardware configuration:

Virtualized Environment with Vmware

  • OS (e.g. from /etc/os-release):
NAME="Rocky Linux"
VERSION="8.9 (Green Obsidian)"
ID="rocky"
ID_LIKE="rhel centos fedora"
VERSION_ID="8.9"
PLATFORM_ID="platform:el8"
PRETTY_NAME="Rocky Linux 8.9 (Green Obsidian)"
ANSI_COLOR="0;32"
LOGO="fedora-logo-icon"
CPE_NAME="cpe:/o:rocky:rocky:8:GA"
HOME_URL="https://rockylinux.org/"
BUG_REPORT_URL="https://bugs.rockylinux.org/"
SUPPORT_END="2029-05-31"
ROCKY_SUPPORT_PRODUCT="Rocky-Linux-8"
ROCKY_SUPPORT_PRODUCT_VERSION="8.9"
REDHAT_SUPPORT_PRODUCT="Rocky Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="8.9"
  • Kernel (e.g. uname -a):

4.18.0-477.27.1.el8_8.x86_64 #1 SMP Wed Sep 20 15:55:39 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

  • Install tools: N/A
  • Others: N/A

possible cause of the problem

Kube-scheduler component config (KubeSchedulerConfiguration) kubescheduler.config.k8s.io/v1beta3 is removed in v1.29. Migrate kube-scheduler configuration files to kubescheduler.config.k8s.io/v1

Validating issue:

check stork-config configmap content

# kubectl get cm -n portworx stork-config -o yaml| grep kubescheduler\.conf  
    
    apiVersion: kubescheduler.config.k8s.io/v1beta3
          apiVersion: kubescheduler.config.k8s.io/v1beta3
          apiVersion: kubescheduler.config.k8s.io/v1beta3
          apiVersion: kubescheduler.config.k8s.io/v1beta3
          apiVersion: kubescheduler.config.k8s.io/v1beta3
          apiVersion: kubescheduler.config.k8s.io/v1beta3
          apiVersion: kubescheduler.config.k8s.io/v1beta3
          apiVersion: kubescheduler.config.k8s.io/v1beta3

Workaround

edit manually configmap and change apiVersion: kubescheduler.config.k8s.io/v1beta3 to apiVersion: kubescheduler.config.k8s.io/v1

@sweepchild
Copy link
Author

sweepchild commented Jun 11, 2024

solved it!

changed operator versionin values.yaml;

portworx.pxOperatorImageVersion: 24.1.0


  apiVersion: kubescheduler.config.k8s.io/v1
          apiVersion: kubescheduler.config.k8s.io/v1
          apiVersion: kubescheduler.config.k8s.io/v1
          apiVersion: kubescheduler.config.k8s.io/v1
          apiVersion: kubescheduler.config.k8s.io/v1
          apiVersion: kubescheduler.config.k8s.io/v1
          apiVersion: kubescheduler.config.k8s.io/v1
          apiVersion: kubescheduler.config.k8s.io/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

1 participant