KubeSchedulerArgs won't work with Release v0.1.7

[philjb]

Issue

This is minor/niche, but I want to docuement that because pr #54 did not regenerate the CRD spec for the controlplane, one cannot use the kubeScheduleArgs field (KThreesControlPlane.spec.kthreesConfigSpec.serverConfig.kubeSchedulerArgs) in the v0.1.7 release.

Someone might pull release v0.1.7 and think they can use that field but they won't be able to.

As of writing, Nov 2, 2023, there has been a v0.1.8 release which doesn't have this issue and I'd assume folks would use that (or a future newer release) if starting from scratch.

Ask

I think the only additional effort for this problem is to add a note on the v0.1.7 release saying that feature doesn't work in that release. Otherwise, I think this issue ticket itself will hopefully be enough documentation if someone runs into this problem.

I only ran into myself as I am bisecting k3s versions trying to find something we saw internally.

References

• bug introduced chore: add kube scheduler server args & plumb through to config #54
• bug fixed (included in v0.1.8 release) feat: expose custom labels for control plane machines #59

[lukebond]

maybe the release can be pulled?