The supportability and the plugin crates on the mayastor-extensions repo use the DiskPool type from the k8s-operators crate (from mayastor-control-plane) by include!()-ing it into a code file. This is not typically how we do things for other dependencies. We should use the Cargo crate module tree for this.
This was likely done previously so that the k8s-operators crate could use a different k8s version of Arnavion/k8s-openapi than the supportability. Presently, cargo dependencies have been simplified using the cargo workspace option. It should be easier to move the DiskPool deps to the Cargo.toml.
The supportability and the plugin crates on the mayastor-extensions repo use the DiskPool type from the k8s-operators crate (from mayastor-control-plane) by
include!()-ing it into a code file. This is not typically how we do things for other dependencies. We should use the Cargo crate module tree for this.This was likely done previously so that the k8s-operators crate could use a different k8s version of Arnavion/k8s-openapi than the supportability. Presently, cargo dependencies have been simplified using the cargo workspace option. It should be easier to move the DiskPool deps to the Cargo.toml.