Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Stateless Updater Execution #118

Closed
Tracked by #114
alexander-demicev opened this issue Feb 3, 2025 · 1 comment · May be fixed by kubernetes-sigs/cluster-api#11818
Closed
Tracked by #114

Stateless Updater Execution #118

alexander-demicev opened this issue Feb 3, 2025 · 1 comment · May be fixed by kubernetes-sigs/cluster-api#11818
Assignees
@Danil-Grigorev
Labels
area/in-place-updates area/upstream-proposal

Comments

@alexander-demicev
Copy link
Member

alexander-demicev commented Feb 3, 2025 •
edited
Loading

The machine controller won’t keep a list of updaters anymore. Instead, it will call all registered updaters during every reconciliation loop. Updaters need to be idempotent and should return a status indicating whether they’ve already completed their task.
@alexander-demicev alexander-demicev mentioned this issue Feb 3, 2025
Closed
5 tasks
@alexander-demicev alexander-demicev moved this to Team Backlog in CAPI / Turtles Feb 4, 2025
@alexander-demicev alexander-demicev changed the title Stateless Updater Execution. The machine controller won’t keep a list of updaters anymore. Instead, it will call all registered updaters during every reconciliation loop. Updaters need to be idempotent and should return a status indicating whether they’ve already completed their task. Stateless Updater Execution Feb 4, 2025
@Danil-Grigorev Danil-Grigorev self-assigned this Feb 6, 2025
@Danil-Grigorev Danil-Grigorev moved this from Team Backlog to In Progress (8 max) in CAPI / Turtles Feb 7, 2025
@Danil-Grigorev Danil-Grigorev moved this from In Progress (8 max) to PR to be reviewed in CAPI / Turtles Feb 10, 2025
@Danil-Grigorev Danil-Grigorev mentioned this issue Feb 10, 2025
Open
@alexander-demicev
Copy link
Member Author

Closing this issue as it's only related to the proposal update. We can open a new one to track serial and ordered execution.

@github-project-automation github-project-automation bot moved this from PR to be reviewed to Done in CAPI / Turtles Feb 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Danil-Grigorev Danil-Grigorev

Labels
area/in-place-updates area/upstream-proposal
Projects
CAPI / Turtles
Archived in project
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

✨ Implement Priority and Serial settings for discovered handlers Danil-Grigorev/cluster-api
3 participants
@kkaempf @alexander-demicev @Danil-Grigorev