Nicolas Trangez

Seems to be merged in HEAD.

> > Of course, this implies the kernel and initrd (and whatever else sits in /boot) doesn't fall under dm-verity validation, but the Grub wouldn't check/use these checksums anyway. >...

Going through the [Boot Loader Specification](https://systemd.io/BOOT_LOADER_SPECIFICATION/) and what [systemd-gpt-auto-generator](https://www.freedesktop.org/software/systemd/man/systemd-gpt-auto-generator.html) does with the `XBOOTLDR` partition, it appears to me using said partition for this purpose is fine and as designed. However,...

I haven't had time to work on this, however still very interested in the feature. One more thought: instead of injecting the `roothash` in `grub.cfg`, we could write it in...

(Sorry if this is off-topic, just wondering) Using real GPT partitions for A/B root selection could be cumbersome because partition sizes are somewhat fixed (unless one provisions them with some...

FWIW, we had a similar situation (one dependency, `doit`, pulling in either `pyinotify` or `macfsevents` depending on the platform) requiring us to render and keep our `requirements.in` into two different...

+1. My scenario: use MetalLB to assign VIP(s) to a service, then have the MetalLB controller apply some kind of (soft) anti-affinity to distribute those per-service VIPs across multiple speakers,...

Recent versions of `swagger-codegen` (as used by `kubernetes-client`) have a `typescript-fetch` 'language' type which should be portable across NodeJS and browser (using `portable-fetch`, which is what the generated code uses)....

I figured one could adjust how `kubernetes-client/gen` generates the API bindings, to make it generate `typescript-fetch` code which would then work in the browser, and be done with it. However,...

Goh... not entirely sure about that, to be honest. It should be possible to keep NodeJS and browser libraries in the same 'source tree'. The major pain-point is generated code,...