I just stumbled upon this today: https://kubernetes.io/blog/2026/01/27/cluster-api-v1-12-release/
I.e. CAPI now has support for "in-place update extensions" to do in-place updates instead of the usual replacement. Need to see whether it makes sense to have a bootc-operator update extension integration point there.
Though offhand one big difference is that CAPI still owns the rollout logic, so bootc-operator in that flow would be more of an executor shim for calling bootc switch... so more "bootc" than "operator". :)
At the very least, it would probably make sense to mention this in the PRD CAPI section.
I just stumbled upon this today: https://kubernetes.io/blog/2026/01/27/cluster-api-v1-12-release/
I.e. CAPI now has support for "in-place update extensions" to do in-place updates instead of the usual replacement. Need to see whether it makes sense to have a bootc-operator update extension integration point there.
Though offhand one big difference is that CAPI still owns the rollout logic, so bootc-operator in that flow would be more of an executor shim for calling
bootc switch... so more "bootc" than "operator". :)At the very least, it would probably make sense to mention this in the PRD CAPI section.