Nicole Hubbard

We do not have an official helm chart available. Since when you deploy you will also need to include your templates in the deployment one wasn't made. If you would...

I noticed the federation-rs repo has a `v2.4.5` tag that failed to publish. I pulled it down and built it locally since that seemed to include some fixed for interfaceObjects....

@allenporter I've added some tests that verify that both v1/secrets and CRD secrets are properly handled. Let me know if you want any changes to them or anything.

@a8m (sorry for the direct tag) any chance of getting a review or feedback on this, we would also like to be able to use this feature.

This is the command I used to build it: ``` docker run --rm -t -v $PWD/\_out:/secureboot:ro -v $PWD/\_out:/out -v /dev:/dev --privileged ghcr.io/siderolabs/imager:v1.12.0-alpha.2-16-gc93a9c6b4 \ installer \ --system-extension-image ghcr.io/siderolabs/amd-ucode:20251021@sha256:e64dbc49897ddfdb7ab694b446a25488cdfb7d145f026d63f57026e71593a67c \ --system-extension-image ghcr.io/siderolabs/iscsi-tools:v0.2.0@sha256:e49cc872c25853ed27bce6b5c3ffee281d205c09f03db20f236409581c5f8cb9...

Unfortunately disabling UEFI isn't an option for me. I have upgraded my nodes to the v1.12.0-beta.0 release with an image built by factory and I'm still getting the same error....

> this does have nothing to do with UEFI > > ``` > > ❯ talosctl -n c0r3-gpu1 patch machineconfig --patch @talos-kubelet-patch.yaml > > error constructing client: failed to determine...