Don't enable the v1_13 feature in the k8s-openapi direct dep about kube HOT 2 CLOSED

Hey, thanks for all this info. I'm happy with this reasoning for not enabling k8s-openapi features in kube and letting that be decided by the app themselves. It feels like the better pattern. Will make the change in the next version 👍

AFAIKT, by removing the default feature choice from kube, it should only force it on controller-rs IF it actually needed k8s-openapi features in the first place. That style of CRD only app was my main reason for keeping k8s-openapi behind a feature.

Aside: There's plenty of good reasons to have mutually exclusive features, it's a shame cargo makes it slightly awkward, there's a real need for them if you see the various issues. Have been using static_assertions to help with this recently.

from kube.

Also, thanks a lot for building k8s-openapi it's been essential for building stuff on top of kubernetes. I will likely send some feature requests or questions your way at some point 🙂

from kube.