-
Notifications
You must be signed in to change notification settings - Fork 37
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
[PWX-35604] Update KubeSchedulerConfiguration to api v1 for k8s version 1.25+ #1395
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## master #1395 +/- ##
==========================================
+ Coverage 75.85% 75.86% +0.01%
==========================================
Files 66 66
Lines 18755 18788 +33
==========================================
+ Hits 14227 14254 +27
- Misses 3519 3523 +4
- Partials 1009 1011 +2 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it is okay to transition to the v1 config starting 1.25.
We should just validate the transition works fine in existing cluster. Let's verify that firstly the config is updated correctly. Secondly, this doesn't affect stork scheduler in anyway by scheduling/re-scheduling new and existing workloads.
f82302f
to
e8e6b94
Compare
stork-config map created in a cluster with k8s version 1.27.2
|
stork-config created in cluster with k8s version 1.23
|
…on 1.25+ (#1395) * Update KubeSchedulerConfiguration to api v1 for k8s version 1.25+ * Addressing comments
* [PWX-35604] Update KubeSchedulerConfiguration to api v1 for k8s version 1.25+ (#1395) * Update KubeSchedulerConfiguration to api v1 for k8s version 1.25+ * adding changes missed due to change in order of mine and zoran's commits compared to 23.10.4
Signed-off-by: Omkar Lavangad olavangad@purestorage.com
What this PR does / why we need it:
KubeSchedulerConfiguration v1beta3 is deprecated in v1.26 and is removed in v1.29. We must migrate to KubeSchedulerConfiguration to v1.
Which issue(s) this PR fixes (optional)
Closes #PWX-35604
Special notes for your reviewer:
The scheduler plugin SelectorSpread is removed, instead, use the PodTopologySpread plugin (enabled by default) to achieve similar behavior.
and we are not using SelectorSpread, so the configMaps created are similar in both the cases other than the library being used.Testing Details
Have tested that appropriate configMap/policy resource is created in k8s v 1.21, 1.23 and 1.25 and stork & stork-scheduler come up properly
Stork Extender jenkins job has successfully passed with the new operator changes https://jenkins.pwx.dev.purestorage.com/job/Users/job/omkar/job/extenderMinio/19/