feat: support machine patches on the machine class level

siderolabs / omni

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

Other

395 stars 24 forks source link

feat: support machine patches on the machine class level #374

Closed Unix4ever closed 3 days ago

Unix4ever commented 2 weeks ago

Now the ConfigPatch resources created with omni.sidero.dev/machine-class: <name> label will be assigned to each machine which matches the picked machine class.

It will have higher priority than Machine and Cluster patches but will be overwritten by the ClusterMachine and MachineSet level patches.

Fixes: https://github.com/siderolabs/omni/issues/31

Unix4ever commented 2 weeks ago

smira commented 2 weeks ago

We had a long discussion with Artem and identified two potential directions:

optimize MachineClass by extracting MachineStatus labels to a separate resource to match on (reduce wakeups to only label changes)
instead of full ConfigPatch propagation from the Machine Class on any change, copy MachineClass patches to the Machine as it joins the MachineSet from the MachineClass (less surpises on config patches changes, less computational complexity); also potentially provide a way to force patch sync