tokio 1.0

[clux]

Just a tracking issue for the tokio 0.3 upgrade.

A couple of things needed;

• minor changes in tokio::time for old runtime (if we care anymore)
• reqwest needs to bump it Update tokio to 1.0 seanmonstar/reqwest#1060 (it's in their master, you can use patch (see below), but a kube release blocked on a crates release of reqwest (edit, done))

[jmjoy]

Maybe wait tokio 1.0? Because:

The Tokio team plans to release Tokio 1.0 by the end of December 2020.

https://tokio.rs/blog/2020-10-tokio-0-3

[clux]

Oh, if that's true, then might as well wait with releasing a new version that depends on a new tokio.

However; if the point of a beta is that the ecosystem has some time to test it out, then maybe that date will be delayed? Reqwest and others haven't caught up to the beta yet.

[nightkr]

Tokio 1.0 is out, so 0.3 seems a bit moot now.. :P

[nightkr]

Progress tracker:

• h2 - 0.3.0
• hyper - 0.14.2
• tokio-native-tls - 0.3.0
• hyper-tls - 0.5.0, Upgrade to Tokio 1.0 hyperium/hyper-tls#79
• reqwest - Update to tokio 1.0, bytes 1.0 seanmonstar/reqwest#1076
• kube
• kube-runtime

[clux]

i'll keep this open until we do a release with it in (blocked by reqwest making a release)

[jbg]

For anyone wanting to use a git dependency on kube to try this out, note that dependency patching only works in the root crate of a dependency tree, so you'll need to copy the patch from kube's Cargo.toml into yours:

[patch.crates-io]
# https://github.com/seanmonstar/reqwest/pull/1076 hasn't been released yet
reqwest = { git = "https://github.com/seanmonstar/reqwest.git", rev = "1f425a0244bcd7b4565dceb9076450d951f2ec03" }

[kazk]

reqwest v0.11.0 was released: seanmonstar/reqwest#1133

[clux]

published in kube* 0.47.0