Kubernetes protobuf bindings for kube-rs. WIP. Not yet useable as is.
This library is not currently usable from kube.
For now consider these structs a reference location for Kubernetes structs that are not found in k8s-openapi.
See docs.rs/k8s-pb.
The code generation process consists of 4 steps;
just protos- download and patch protobufsjust swagger- download and transform openapi schemajust codegen- combine info and build with prostjust names- case alignment andcargo fmt
This can be run in one step with just generate.
The k8s-pb crate is generated as a result of this process and then published periodically.
Obtains the version pinned protobufs from upstream:
- https://github.com/kubernetes/api/releases
- https://github.com/kubernetes/apimachinery/releases
- https://github.com/kubernetes/apiextensions-apiserver/releases
- https://github.com/kubernetes/kube-aggregator/releases
- https://github.com/kubernetes/metrics/releases
then does minor transforms to prepare them for building.
Obtains the version pinned swagger openapi schema from upstream:
then applies any needed patches before transforming the schema into a shorter json file containing desired generic information.
This json file complements the protos with type type properties needed for trait implementations.
Runs main.rs, using the outputs from the swagger and protobuf recipes above. In particular;
- The protos are built with prost via
protocand provides aFileDescriptorSetviaConfig::file_descriptor_set_path. - The transformed swagger result json is deserialized through lib.rs into a
HashMap<String, Resource>where the string is a GVK string. - inject generics for each modules in hashmap via
append_trait_impl - Generate a module tree from the seen modules in the loop
- Attach our implemented traits to the generated lib.rs