Correct version of kube

[pisees]

Regarding Installation and "Select a version of kube along with the generated k8s-openapi types corresponding for your cluster version:"

How do I find out the correct versions in my cluster?

[kazk]

kubectl version --short should show versions of your client and server. Something like

Client Vesion: v1.19.4
Server Version: v1.20.2

Use the version matching your server version.

[clux]

Yeah, if you want type safety you gotta get it from somewhere. I wouldn't try to use solution 2 there myself because it's generally super easy to do an upgrade manually:

-use k8s_openapi::api::batch::v1beta::CronJob
+use k8s_openapi::api::batch::v1::CronJob

if you want to dynamically figure out what CronJob is available in the cluster and use that instead, then you can use the discovery api with say a pinned_group. But note that you don't get typesafety of the struct you are serializing into anymore then, because you don't actually know what struct you are getting.

[DevasiaThomas]

@teozkr Cool! Thanks for the example and the recommendation . A follow up question would be in case of solution 2, what would I specify in the Cargo.toml file against features for k8s-openapi?

[nightkr]

@DevasiaThomas You would generally want to specify the oldest K8s version that contains both versions. In this case, that would be v1_21 (since CronJob v1 was introduced in v1.21 and you don't use anything introduced in v1.22+).

[DevasiaThomas]

@clux Yup, I see your point. In an ideal world this would work fine. But I'll try out @teozkr first recommendation and then use solution 2 incase there is something I cannot absolutely get without using it.

[DevasiaThomas]

@DevasiaThomas You would generally want to specify the oldest K8s version that contains both versions. In this case, that would be v1_21 (since CronJob v1 was introduced in v1.21 and you don't use anything introduced in v1.22+).

Awesome, that makes sense! Thanks again :)