Skip to content

Add support for in-place update contracts#866

Open
alexander-demicev wants to merge 2 commits intorancher:mainfrom
alexander-demicev:inplaceskeleton
Open

Add support for in-place update contracts#866
alexander-demicev wants to merge 2 commits intorancher:mainfrom
alexander-demicev:inplaceskeleton

Conversation

@alexander-demicev
Copy link
Copy Markdown

@alexander-demicev alexander-demicev commented Mar 25, 2026

What this PR does / why we need it:

This PR add support for in-place update contracts. It requires some internal CAPI functions to be made public but that's likely not going to happen anytime soon kubernetes-sigs/cluster-api#13507. I added a CAPI package that includes all required code and keeps it separated. We can later drop the package as we make functions public.

The carried code from CAPI is added with a separate commit to make reviews easier.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #865

Special notes for your reviewer:

Checklist:

  • squashed commits into logical changes
  • includes documentation
  • adds unit tests
  • adds or updates e2e tests

@alexander-demicev alexander-demicev requested a review from a team as a code owner March 25, 2026 15:27
@alexander-demicev alexander-demicev moved this to PR to be reviewed in CAPI / Turtles Mar 25, 2026
@alexander-demicev alexander-demicev force-pushed the inplaceskeleton branch 2 times, most recently from 47b1180 to 83d72dd Compare March 29, 2026 12:37
@alexander-demicev alexander-demicev changed the title Setup skeleton for in-place updates implementation [WIP] Add support for in-place update contracts Mar 29, 2026
@kkaempf kkaempf moved this from PR to be reviewed to Blocked in CAPI / Turtles Mar 31, 2026
@alexander-demicev alexander-demicev changed the title [WIP] Add support for in-place update contracts Add support for in-place update contracts Apr 15, 2026
Signed-off-by: Alex Demicev <alex.demicev@lambdal.com>
@furkatgofurov7 furkatgofurov7 added area/controlplane Indicates an issue or PR related to the control plane provider kind/feature and removed status/waiting-for-upstream labels Apr 15, 2026
@furkatgofurov7 furkatgofurov7 moved this from Blocked to PR to be reviewed in CAPI / Turtles Apr 15, 2026
@furkatgofurov7
Copy link
Copy Markdown
Contributor

@alexander-demicev looks like capi-controller-manager is not coming up in e2e tests, maybe feature gate introduction broke it?

Signed-off-by: Alex Demicev <alex.demicev@lambdal.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/controlplane Indicates an issue or PR related to the control plane provider kind/feature

Projects

Status: PR to be reviewed

Development

Successfully merging this pull request may close these issues.

[In-place updates] Introduce a feature gate

4 participants