k8s-openapi
quibble
Our great sponsors
k8s-openapi | quibble | |
---|---|---|
7 | 10 | |
360 | 2,010 | |
- | - | |
8.3 | 7.3 | |
12 days ago | 5 months ago | |
Rust | C | |
Apache License 2.0 | GNU Lesser General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
k8s-openapi
-
WinBtrfs – an open-source btrfs driver for Windows
It's called sans-io in Python land, which is where I heard it first.
https://sans-io.readthedocs.io/
I did it for one of my projects back in 2018 https://github.com/Arnavion/k8s-openapi/commit/9a4fbb718b119...
-
The bane of my existence: Supporting both async and sync code in Rust
Another option is to implement your API in a sans-io form. Since k8s-openapi was mentioned (albeit for a different reason), I'll point out that its API gave you a request value that you could send using whatever sync or async HTTP client you want to use. It also gave you a corresponding function to parse the response, that you would call with the response bytes however you got them from your client.
https://github.com/Arnavion/k8s-openapi/blob/v0.19.0/README....
(Past tense because I removed all the API features from k8s-openapi after that release, for unrelated reasons.)
-
Welcome to Comprehensive Rust
Macro expansion is slow, but only noticeably in the specific situation of a) third-party proc macros, b) a debug build, and c) a few thousand invocations of said proc macros. This is because debug builds compile proc macros in debug mode too, so while the macro itself compiles quickly (because it's a debug build), it ends up running slowly (because it's a debug build).
I know this from observing this on a mostly auto-generated crate that had a couple of thousand types with `#[derive(serde::)]` on each. [1]
This doesn't affect most users, because first-party macros like `#[derive(Debug)]` etc are not slow because they're part of rustc and are thus optimized regardless of the profile, and even with third-party macros it is unlikely that they have thousands of invocations. Even if it is* a problem, users can opt in to compiling just the proc macros in release mode. [2]
[1]: https://github.com/Arnavion/k8s-openapi/issues/4
[2]: https://github.com/rust-lang/cargo/issues/5622
-
OpenAPI Generator allows generation of API client libraries from OpenAPI Specs
>OpenAPI Generator allows generation of API client libraries from OpenAPI Specs
It does, but the generated code can be very shitty for some combinations of spec and output language. I maintain Rust bindings for the Kubernetes API server's API, and I chose to write my own code generator instead. The README at https://github.com/Arnavion/k8s-openapi has more details.
-
Any good toy Rust project for k8s application?
k8s_openapi - https://github.com/Arnavion/k8s-openapi
-
Approaches for Chaining Access to Deeply Nested Optional Structs
For example: I have a routine that checks the value of (from k8s-openapi): Ingress -> IngressStatus -> LoadBalancerStatus -> Vec[0] -> String
-
Writing a Kubernetes CRD Controller in Rust
As the maintainer of the Rust bindings that the library used in the article (kube) is backed by, I can confirm that Kubernetes' openapi spec requires a lot of Kubernetes-specific handling to generate a good client than generic openapi generators do not provide.
See https://github.com/Arnavion/k8s-openapi/blob/master/README.m... for a full description.
I also confirm that I keep it up-to-date with Kubernetes releases and have been doing so for the ~3 years that it's been around. Not just the minor ones every few months, but even the point ones; these days the latter usually only involves updating the test cases instead of code changes and they're done within a few hours of the upstream release.
quibble
-
WinBtrfs – an open-source btrfs driver for Windows
Not in its own. You also need a different boot loader. The author has an implementation called Quibble [0] that also supports btrfs.
[0] https://github.com/maharmstone/quibble
- Life with dual boot
- Installing Windows bare metal on a ZFS volume
- [Dual boot] Upgrading to Windows 11 caused GRUB not to show on startup
-
Anyone using openzfs on Windows on a daily basis? Can ZVOLs be used to back WSL?
A custom bootloader for windows that works for WinBTRFS and others may eventually allow booting on mostly/entirely ZFS instead of symlinking user folders to a dataset or whatever. If ZFS isn’t ready yet, I’ll just try WinBTRFS instead.
-
ZFSBootMenu – A boot loader to manage ZFS boot environments for Linux
It's not ZFS, but let's check this with btrfs https://github.com/maharmstone/quibble
- "file extensions are hints as to what might be in the file, not a standard."
-
Anyone think it's possible to force load Win 11 on a Dell Venue 8 Pro?
See this project: https://github.com/maharmstone/quibble/issues/2
- Gabe Newell Pushes Back Against Closed Platforms, Says Openness is 'PC's Superpower'
-
Installing windows on BTRFS
It is technically possible, but you'll need to use an alternate boot loader for that: https://github.com/maharmstone/quibble
What are some alternatives?
kube - Rust Kubernetes client and controller runtime
skywater-pdk - Open source process design kit for usage with SkyWater Technology Foundry's 130nm node.
fusionauth-openapi - FusionAuth OpenAPI client
btrfs - WinBtrfs - an open-source btrfs driver for Windows
go - The Go programming language
zfs - OpenZFS on Linux and FreeBSD
spectrum - OpenAPI Spec SDK and Converter for OpenAPI 3.0 and 2.0 Specs to Postman 2.0 Collections. Example RingCentral spec included.
ZFSin - OpenZFS on Windows port
smithy - Smithy is a protocol-agnostic interface definition language and set of tools for generating clients, servers, and documentation for any programming language.
openzfs - OpenZFS on Linux and FreeBSD
tokio - A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...
MediaCreationTool.bat - Universal MCT wrapper script for all Windows 10/11 versions from 1507 to 21H2!