Update docs and finalize for 0.72.0 #909
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Plan on releasing 0.72.0 tomorrow (with or without the outstanding docs thing).
Stuff to put in highlights:
(NB: TODOs blocked by release on docs.rs)
Ergonomics improvements
A new
runtime::WatchSteamExt
(#899 + #906) allows for simpler setups for streams fromwatcher
orreflector
.The
util::try_flatten_*
helpers have been marked as deprecated since they are not used in the new pipeline.A new
reflector:store()
fn allows simpler reflector setups #907:Additional conveniences getters/settes to
ResourceExt
for manged_fields and creation_timestamp #888 + #898, plus aGroupVersion::with_kind
path to a GVK, and aTryFrom<TypeMeta> for GroupVersionKind
in #896.CRD Version Selection
Managing multiple version in CustomResourceDefinitions can be pretty complicated, but we now have helpers and docs on how to tackle it.
A new function
kube::core::crd::merge_crds
(TODO: docs.rs link) have been added (in #889) to help push crd schemas generated by kube-derived crds with different#[kube(version)]
properties. TODO: link to kube-derive segment.A new example showcases how one can manage two or more versions of a crd and what the expected truncation outcomes are when moving between versions.
Examples
Examples now have moved to
tracing
for its logging, respectsRUST_LOG
, and namespace selection via the kubeconfig context. There is also a larger kubectl example showcasingkubectl apply -f yaml
https://github.com/kube-rs/kube-rs/blob/7715cabd4d1976493e6b8949471f283df927a79e/examples/kubectl.rs#L149-L170 as well askubectl {edit,delete,get,watch}
via #885 + #897.