What problem are you trying to solve?

Available in 1.33 in the openapi spec as

https://github.com/kube-rs/k8s-pb/blob/e6ab15b76711fd9964977ffa88943c5e79779f75/k8s-pb-codegen/openapi/transformed.json#L1639C18-L1649

There's an article on it in https://itnext.io/kubernetes-1-33-resizing-pods-without-the-drama-finally-88e4791be8d1

Describe the solution you'd like

Standard subresource handling. Lots of examples in this old master issue
Gated on k8s_if_ge_1_33.

AFAIKT from the article the data you pass in is a full Pod so we could have a typed interface literally taking a Pod.

Describe alternatives you've considered

Only support it via the dynamic Api::verb_subresource interface.

We don't strictly need it because this dynamic interface exists, but if anyone want to make it better, happy to take a PR.

Documentation, Adoption, Migration Strategy

Should be a straight feature-add in kube-core and kube-client in the two subresource.rs files.

Target crate for feature

kube-client, kube-core