pool-lifecycle-controller coordinates the deletion of Cluster API
(CAPI) compute nodes with graceful eviction of the IronCore
Machines running on them. When CAPI replaces or deletes a compute node (during upgrades,
scale-down, or remediation), the underlying node backs an IronCore MachinePool, and deleting
it while IronCore VMs are still running would drop those workloads.
Note: This controller does not define any CRDs of its own. It reconciles the external CAPI
Machineand IronCoreMachine/MachinePooltypes, so there is nothing tomake installand noconfig/samplesto apply.
We'd love to get feedback from you. Please report bugs, suggestions or post questions by opening a GitHub issue.
Copyright 2025 SAP SE or an SAP affiliate company and IronCore contributors. Please see our LICENSE for copyright and license information. Detailed information including third-party components and their licensing/copyright information is available via the REUSE tool.
