Feature openapi has hardcoded k8s-openapi's feature to v1_15

[divoxx]

Currently, trying to use another version of the openapi (i.e. v1_14) causes compilation to fail with the following error:

Both v1_14 and v1_15 features are enabled on the k8s-openapi crate. Only one feature can be enabled at the same time.

The feature indicates which version of Kubernetes the k8s-openapi crate should support.

If you have enabled both of these features yourself, please remove one of them. If you are writing a library crate, do not enable any features at all. Library crates *must not* enable any features on the k8s-openapi crate.

If you have not enabled one or both of these features yourself, then one of the library crates in your dependency graph *has*. Locate which library crates in your dependency graph depend on k8s-openapi and enable one of its features, and file a bug against them. You can search your Cargo.lock for "k8s-openapi" to discover these crates.

As described in k8s-openapi, libraries should not specify a version/feature. Is this feasible in this library?

[clux]

Oh, that sounds wrong :(

Do you mind pasting how you are using kube + k8s-openapi in Cargo.toml? I thought this would't happen with default-features set to false, but maybe we need to remove the pin there.

[divoxx]

Hi @clux

I was testing kube-rs in a fresh application against a 1.14 cluster, so I've added the following dependencies:

[dependencies]
kube = { version = "0.18.1", features = ["openapi"] }
k8s-openapi = { version = "0.6.0", default-features = false, features = ["v1_14"] }

Which resulted in that error. I think you need to get rid of this chunk and keep only the dev-dependencies with a hard coded version.

[clux]

Have taken out all features by default. Think master is now better.

Thanks for the report!

[clux]

releasing in 0.20.0