build(deps): bump kube from 0.67.0 to 0.75.0

[dependabot]

Bumps kube from 0.67.0 to 0.75.0.

Release notes

Sourced from kube's releases.

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 kube-rs/kube-rs#929
• Add conditions::is_job_completed by @​clux in kube-rs/kube-rs#935

Changed

• Deprecate ResourceExt::name in favour of safe name_* alternatives by @​clux in kube-rs/kube-rs#945

Removed

• Remove #[kube(apiextensions)] flag from kube-derive by @​clux in kube-rs/kube-rs#920

Fixed

• Document every public derived fn from kube-derive by @​clux in kube-rs/kube-rs#919
• fix applier hangs which can happen with many watched objects by @​moustafab in kube-rs/kube-rs#925
• Applier: Improve reconciler reschedule context to avoid deadlocking on full channel by @​teozkr in kube-rs/kube-rs#932
• Fix deserialization issue in AdmissionResponse by @​clux in kube-rs/kube-rs#939
• Admission controller example fixes by @​Alibirb in kube-rs/kube-rs#950

New Contributors

• @​moustafab made their first contribution in kube-rs/kube-rs#925
• @​phroggyy made their first contribution in kube-rs/kube-rs#929
• @​Alibirb made their first contribution in kube-rs/kube-rs#950

Full Changelog: kube-rs/kube@0.73.0...0.74.0

0.73.1

Highlights

... (truncated)

Changelog

Sourced from kube's changelog.

0.75.0 / 2022-09-21

0.74.0 / 2022-07-09

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 kube-rs/kube-rs#929
• Add conditions::is_job_completed by @​clux in kube-rs/kube-rs#935

Changed

• Deprecate ResourceExt::name in favour of safe name_* alternatives by @​clux in kube-rs/kube-rs#945

Removed

• Remove #[kube(apiextensions)] flag from kube-derive by @​clux in kube-rs/kube-rs#920

Fixed

• Document every public derived fn from kube-derive by @​clux in kube-rs/kube-rs#919
• fix applier hangs which can happen with many watched objects by @​moustafab in kube-rs/kube-rs#925
• Applier: Improve reconciler reschedule context to avoid deadlocking on full channel by @​teozkr in kube-rs/kube-rs#932
• Fix deserialization issue in AdmissionResponse by @​clux in kube-rs/kube-rs#939
• Admission controller example fixes by @​Alibirb in kube-rs/kube-rs#950

0.73.1 / 2022-06-03

Highlights

This patch release fixes a bug causing applier and Controller to deadlock when too many Kubernetes object change events were ingested at once. All users of applier and Controller are encouraged to upgrade as quickly as possible. Older versions are also affected, this bug is believed to have existed since the original release of kube_runtime.

... (truncated)

Commits

• 575b3f4 release 0.75.0
• 69a5374 bumps for 0.75
• a65c249 Upgrade k8s-openapi to 0.16 (#1008)
• cc2a2b9 Add support for CRD ConversionReview types (#999)
• 15faafb Merge pull request #1006 from teozkr/chore/avoid-send-unwraps
• 65a0627 Merge branch 'master' into chore/avoid-send-unwraps
• 79e4e09 Config: New incluster and incluster_dns constructors (#1001)
• 2001e30 Merge branch 'master' into chore/avoid-send-unwraps
• b757859 Merge pull request #1007 from olix0r/ver/deny
• 09c5cf6 Update deny.toml for idna
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)