gateway-api-rs
gateway-api-rs copied to clipboard
kube-rs
Kubernetes Gateway API bindings for Rust
Currently the Status Reason/Conditions are missing from the generated types. See [`RouteConditionReason`](https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io%2fv1beta1.RouteConditionReason) and [`RouteConditionType`](https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io%2fv1beta1.RouteConditionReason). These are not directly referenced by the openapi schema because they are implicitly considered the String...
It would dramatically improve the crate's usability if instead of defining discrete types for every nested object within a CRD, compatible/identical types were defined once and automatically reused. For example,...
There are a lot of constants related to the `Condition` object that are a part of the Go API, but they're not reflected in the CRD since the `Condition` API...
Currently we're not running [doctests](https://doc.rust-lang.org/rustdoc/write-documentation/documentation-tests.html) in CI due to a problem with our generated API code from `kopium`, wherein the docs generated trigger and then fail testing attempts. The purpose...
Using this crate requires pinning kube-rs and k8s-openapi versions and the k8s-openapi v1_29 feature
I'm trying to use this crate in a project with more recent versions of `kube-rs` and `k8s-openapi` and it's proving pretty difficult because of pinned dependency versions. This looks like...
I just noticed that the Gateway APIs v1.2.0 is out. It'd great to have support for it here. https://github.com/kubernetes-sigs/gateway-api/releases/tag/v1.2.0 EDIT: (Sorry about the issue title spam 😞)
We need to upgrade our `hyper` dependency to `v1.x.x`. This includes backwards incompatible changes that we will need to accommodate for.
Similar in nature to #98 Upstream: https://github.com/kubernetes-sigs/gateway-api/blob/main/apis/v1/shared_types.go
The [Documentation](https://docs.rs/gateway-api/latest/gateway_api/index.html) for this crate on docs.rs is a bit light right now and the purpose of this issue is to expand on those. This should include some high level...
We need an example in `gateway-api/examples` for building a [kube-rs controller] with Gateway API. [kube-rs controller]:https://kube.rs/controllers/intro/