Tracking issue for In-place Updates implementation

[alexander-demicev]

This is a tracking issue for the implementation of in-place updates. At the moment, it only covers the work required for the initial phase of the project to reach the experimental (alpha) stage.

The design and approach are described in the in-place updates proposal.

• Add InPlaceUpdates feature gate

• Introduce Runtime Hook API changes, see examples section of the proposal for details.

  • Add ExternalUpdate runtime hook
  • Define API contract for CanUpdateMachineRequest and CanUpdateMachineResponse
  • Define API contract for UpdateMachineRequest and UpdateMachineResponse

• Create reference external updater (CAPD Kubeadm Updater)

  • Set up the project structure
  • Implement handlers for both runtime endpoints
  • Implement container commands for upgrading Kubernetes components
  • Provide config samples for the updater

• Modify core controllers

  • KubeadmControlPlane controller updates

    • See these parts of the proposal for details:

      • High-level flow
      • Deciding the update strategy
      • KCP updates

  • MachineDeployment controller updates

    • See these parts of the proposal for details:

      • High-level flow
      • Deciding the update strategy
      • MachineDeployment updates

  • Machine controller modifications

    • See these parts of the proposal for details:

      • High-level flow
      • Deciding the update strategy
      • Machine updates

• Set up E2E testing

  • Implement E2E suite that uses the CAPD Kubeadm Updater

• Create documentation

  • Feature flag configuration
  • New runtime hook and its API contracts
  • Updater structure and logic
  • Guide to implementing extensions
  • Explanation of the CAPD Kubeadm Updater
  • Tutorials for usage

[k8s-ci-robot]

This issue is currently awaiting triage.

If CAPI contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[k8s-ci-robot]

@alexander-demicev: The label(s) /label kind/design cannot be applied. These labels are supported: api-review, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, team/katacoda, refactor, ci-short, ci-extended, ci-full. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

In response to this:

/label kind/design

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[alexander-demicev]

/kind design