k8s-openapi
k8s-openapi copied to clipboard
Arnavion
Rust definitions of the resource types in the Kubernetes client API
This is an alternative approach suggested in #120 TODO: * [x] seems like due to using traits, I don't need all that extra type tracking - remove * [x] validate...
This is an initial implementation of the idea described in #80 The goal is to make all these generated types much more usable directly in code in a semi-DSL way...
I'm [researching implementing a kind-of-helm-replacement](https://github.com/clux/kube-rs/issues/343) that would generate input for `kubectl apply -f -` be just executing Rust source code. In such tool I would like to reuse types generates...
New to Rust - Trying to build a k8s operator. When testing what I have so far, attempting to build causes the above-mentioned error. Thing is, my `Cargo.toml` does specify...
https://github.com/kubernetes/kubernetes/blob/9d278e622427d307d50c1c2440b556005e2f8769/CHANGELOG/CHANGELOG-1.24.md#openapi-v3 >Kubernetes 1.24 offers beta support for publishing its APIs in the OpenAPI v3 format. Compare with the v2 schema to see if anything is documented more precisely, eg using...
Here is an example secret that can be returned: ```json { "metadata": { "name": "a-cert", "namespace": "ns", "selfLink": "/api/v1/namespaces/ns/secrets/a-cert", "uid": "c18dd343-b8ba-11e9-94ec-83289476e83dc0", "resourceVersion": "1082189042", "creationTimestamp": "2023-08-07T02:26:26Z" }, "data": { "tls.crt": null,...
This is a draft because currently, it still fails on `metrics.k8s.io`.
# Repro ```rust use k8s_openapi::api::apps::v1::StatefulSetSpec; println!("{}", serde_yaml::to_string(&StatefulSetSpec::default()).unwrap()); ``` ## Expected ```yaml --- template: {} ``` ## Produced ```yaml --- selector: {} serviceName: "" template: {} ``` # Why is this...
The API server exposes its spec at [`/openapi/v2`](https://kubernetes.io/docs/concepts/overview/kubernetes-api/#openapi-and-swagger-definitions) Is it worth allowing a user to run `k8s-openapi-codegen` against this endpoint to generate a custom API bindings crate? --- Edit: Starting...
These are common to spec-generated clients of all languages, but it helps Rust devs who haven't used the other languages' clients before. - Resource types are under `api`, etc, then...