0.74.0
Highlights
Polish, bug fixes, guidelines, ci improvements, and new contributors
This release features smaller improvements/additions/cleanups/fixes, many of which are from new first-time contributors! Thank you everyone!
The listed deadlock fix was backported to 0.73.1.
We have also been trying to clarify and prove a lot more of our external-facing guarantees, and as a result:
- We have codified our Kubernetes versioning policy
- The Rust version policy has extended its support range
- Our CI has been extended
ResourceExt::name
deprecation
A consequence of all the policy writing and the improved clarity we have decided to deprecate the common ResourceExt::name
helper.
This method could panic and it is unexpected for the users and bad for our consistency. To get the old functionality, you can replace any .name()
call on a Kubernetes resources with .name_unchecked()
; but as the name implies, it can panic (in a local setting, or during admission). We recommend you replace it with the new ResourceExt::name_any
for a general identifier:
-pod.name()
+pod.name_any()
What's Changed
Added
- Add support for passing the
fieldValidation
query parameter on patch by @phroggyy in #929 - Add
conditions::is_job_completed
by @clux in #935
Changed
Removed
Fixed
- Document every public derived fn from kube-derive by @clux in #919
- fix applier hangs which can happen with many watched objects by @moustafab in #925
- Applier: Improve reconciler reschedule context to avoid deadlocking on full channel by @teozkr in #932
- Fix deserialization issue in AdmissionResponse by @clux in #939
- Admission controller example fixes by @Alibirb in #950
New Contributors
- @moustafab made their first contribution in #925
- @phroggyy made their first contribution in #929
- @Alibirb made their first contribution in #950
Full Changelog: 0.73.0...0.74.0