Nathan Snow

Also, outside of the basic setup, there seems to be no production oriented deployment documentation. It would be useful for those of us that are evaluating this for professional reasons...

I think the easiest solution that comes to mind is, being able to select multiple ServerClasses when defining the MetalMachineTemplate. Possibly using a ServerClass label, that exists on multiple ServerClasses,...

/I wasn't aware of the disk selectors. That will be helpful regarding install disks. However, let me lay out a scenario and maybe that will help explain what my issue...

Hmm, I think that will work, making another machine deployment. I should be able to duplicate the below resources for each set of hardware. Not exactly ideal, a lot of...

> Just in case, you can have multiple worker machine deployments for a single cluster this way you could have multiple worker sets coming from multiple ServerClasses. You can also...

> CAPI only natively supports upgrades by replacing nodes. Sidero will deliver config to the machine only once. Gotcha, not a big deal, Sidero/Talos makes that process easy and I...

> Ok, good to know. I will revist that. I appreciate the clarification you have provided so far. This has been really helpful. For the rolling of a node to...

> `talosVersion` is not the Talos version you're installing, it's the machine config generation contract: https://github.com/siderolabs/cluster-api-bootstrap-provider-talos/#usage > > The version of Talos you're installing is defined by the `Environment` in...

+1 for this. I have client's that can't manage a cert store, and I need the full chain including the root. We use a Vault PKI for our CAs ftr.

So, I didn't realize there was no support for this. I just updated my saltstack, found that some necessary docker features aren't supported in the `docker-formula`, spent hours updating their...