Skip to content

Conversation

@Unix4ever
Copy link
Member

Now graceful config rollout is handled by the
ClusterMachineConfigStatusController.
It calculates the available update quota by adding finalizers on the ClusterMachine resources. By counting the resources with the finalizers it tracks the remaining quota.
It now also calculates the pending changes which are not yet applied to the machine in the MachinePendingUpdates.

Pending changes are not yet shown in the UI anywhere.

Fixes: #1929

@Unix4ever Unix4ever added the integration/e2e Triggers all e2e tests for Omni label Dec 26, 2025
@talos-bot talos-bot moved this from To Do to In Review in Planning Dec 26, 2025
@github-project-automation github-project-automation bot moved this to To Do in Planning Dec 26, 2025
@Unix4ever Unix4ever force-pushed the graceful-rollout-machine-config-status branch from e3835f0 to 2e7580e Compare December 29, 2025 13:19
Now graceful config rollout is handled by the
`ClusterMachineConfigStatusController`.
It calculates the available update quota by adding finalizers on the
`ClusterMachine` resources. By counting the resources with the
finalizers it tracks the remaining quota.
It now also calculates the pending changes which are not yet applied to
the machine in the `MachinePendingUpdates`.

Pending changes are not yet shown in the UI anywhere.

Fixes: siderolabs#1929

Signed-off-by: Artem Chernyshev <artem.chernyshev@talos-systems.com>
@Unix4ever Unix4ever force-pushed the graceful-rollout-machine-config-status branch from 2e7580e to ed7e446 Compare December 29, 2025 13:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

integration/e2e Triggers all e2e tests for Omni status/ok-to-test

Projects

Status: In Review

Development

Successfully merging this pull request may close these issues.

[refactor] Rework the config apply rollout to work directly with ClusterMachineConfig

2 participants