Benjamin Landsteiner

I am using the latest sidero, and for this example talos 1.1.1: ``` [root@dill04 demo]# clusterctl upgrade plan Checking cert-manager version... Cert-Manager is already up to date Checking new release...

There was more discussion on this on the sidero slack last fall, but that has aged out so I thought I'd add in some of those learnings here for posterity....

If you've confirmed it's fixed, then go ahead and close it. I haven't tried this in a few months, but might be able to try again sometime in October.

A few updates in case it's helpful. - I've provisioned workload clusters when the management cluster was itself created with `talosctl cluster create` using docker, and on a baremetal talos...

Yes - I am using the latest released versions of the providers. ``` [root@dill04 demo-1.2]# clusterctl --kubeconfig-context admin@bootstrap upgrade plan Checking cert-manager version... Cert-Manager is already up to date Checking...

We would use the following protocols in our talos environment: 1. NFSv4 (including pNFS) 2. NVMe/TCP