fix: properly generate machine config input versions in the migration - Githubissues

siderolabs / omni

SaaS-simple deployment of Kubernetes - on your own hardware.

Other

397 stars 23 forks source link

fix: properly generate machine config input versions in the migration #323

Closed Unix4ever closed 4 weeks ago

Unix4ever commented 4 weeks ago

Looks like the test was broken in two places too and wasn't verifying anything:

the status was missing the schematic and so the resources were just skipped by the ClusterMachineConfig controller.
the ClusterMachineTalosVersion resources were ignored in the migration method and not created in the test.

So basically it was a bit outdated. Now it's in sync and I've checked that the test is failing with the buggy code.

Unix4ever commented 4 weeks ago

/m