unrecognized format "uint32"

[SylChamber]

When deploying Bindy in Kubernetes 1.36.2 using the bindy CLI 0.5.2, the following warning is reported for the Bind9Clusters CRD:

Warning: unrecognized format "uint32"

There seems to be a related issue in the Kubernetes SIGS: controller-gen: Why uint32/uint64 are mapped to int32/int64? - kubernetes-sigs/controller-tools

In the issue, someone reports that Kubernetes is based on OpenAPI 3.0. uint32 isn't part of the spec: OpenAPI Specification v3.0.0 - Data Types, that would explain the warning.

FYI I'm deploying Bindy in a Talos Linux 1.13.5 test cluster in QEMU VMs, and instead of using the CLI, I generated YAML from dry runs of bindy bootstrap operator and bindy bootstrap scout then split the YAML in individual files with the slice plugin installed with krew. That's so I can push that version of Bindy to git as a kustomization and deploy it GitOps-style with Flux CD.

We met at the CNCF Québec meetup on June 10th, BTW. I really like the idea of Bindy. I was going to use CoreDNS in my home network (Talos on 3 mini PCs), but after having seen Bindy, that's what I'm going to use, it's so much simpler and fits perfectly in Kubernetes. I'm also considering using it at work. 😁

[ebourgeois]

Salut Sylvain! Yes, I remember meeting! really glad you are using it and happy to help with deployments!

Your report is quite interesting, i have not seen this, as I am running on 1.35. Let me look into this some more and get back to you,.

Can I ask why you chose Talos and not Kairos? I would HIGHLY recommend Kairos over Talos for many reasons, but here's a blog post I did on cncf.io: https://www.cncf.io/blog/2026/05/13/building-a-cloud-native-platform-from-the-ground-up-with-kairos-k0rdent-and-bindy/

cc: @mauromorales

[SylChamber]

Can I ask why you chose Talos and not Kairos? I would HIGHLY recommend Kairos over Talos for many reasons, but here's a blog post I did on cncf.io: https://www.cncf.io/blog/2026/05/13/building-a-cloud-native-platform-from-the-ground-up-with-kairos-k0rdent-and-bindy/

Yes, that's because I hadn't heard of it! (I'm way behind on my technological watch!)

I was looking for a purpose-built OS for Kubernetes and found Talos first. I had a look at Flatcar Container Linux and I didn't want its configuration method. And it's frankly dated, being based on CoreOS. I chose Talos even though I prefer CNCF projects, because I wanted the littlest effort in OS maintenance.

However, it's all manual, so I do have maintenance chores to do. I have to run a command with its CLI to upgrade Talos Linux on my nodes, and another command to upgrade Kubernetes.

The fact that Talos isn't a CNCF project is something that was bothering me, but I accepted the risk. I was considering giving Flatcar Container Linux a try, however, to reduce the maintenance efforts.

I'd also like a solution which I can easily virtualize for a test environment. Preferably with incus which I find so much easier. With Talos, it's not perfect and limited to QEMU VMs or docker containers. (I don't like running docker on my Fedora Linux desktop, as I much prefer podman.)

I'd say Kairos and the new Hadron Linux fit my needs perfectly. (I particularly like the choice of systemd, which allows extensions.) Wow. I'm sorry I missed that project in my search. Incus seems to have a provider for CAPI.

Many thanks for the tip!

[mauromorales]

@SylChamber happy to hear any feedback (good or bad) if/when you try Kairos and Hadron.

[wrkode]

thanks for the callout @ebourgeois.
@SylChamber, I will look into Incus for Kairos CAPI integration. we've just completed CAPK, CAPV and CAPM3. I'll look into Incus next.

[SylChamber]

Thanks. I've been reading on Kairos, Hadron and k0s, and looking up how I could create a cluster with libvirt or Incus, terraform or Cluster API. I think I could use k0smotron CAPI providers to deploy a Hadron k0s cluster in Incus VMs with Cluster API.