Update kubescheduler.config.k8s.io version for k8s 1.29

[gregi2n]

Bug

Stork-scheduler fails to deploy on k8s 1.29 because kubescheduler.config.k8s.io/v1beta3 is now deprecated and should just be v1

What you expected to happen:
It deploys successfully

How to reproduce it (as minimally and precisely as possible):
Deploy stork to a cluster with k8s version 1.29

Anything else we need to know?:

I'm using portworx and this is the file specs/stork-deployment.yaml

[nabiltntn]

Hi,
Is there any issue to upgrade the kubescheduler.config.k8s.io version to v1 ? When used with Portworx operator with storagecluster, the generated stork-config configmap still contains v1beta3 which leads to stork scheduler not able to start upon redeployment.

The only "workaround" for the moment, is to edit the generated stork-config configmap and immediately delete one of stuck stork-scheduler pods to allow to start one new pod correctly before the operator reset the configmap again back to generated config with v1beta3.

[pp511]

Hi,
Which Portworx operator version is being used here?
The recent operator versions deploy kubescheduler configuration V1 CR.
I would suggest upgrading your Operator version >= 23.10.4.
Regards,
Priyanshu

[nabiltntn]

@pp511 Thank you, the issue was fixed by deploying 23.10.5 version of the operator. The good news is that PX upgrade itself was not required.