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

Support InPlaceUpdate deployment strategy #944

Open
11 tasks
acumino opened this issue Oct 7, 2024 · 2 comments
Open
11 tasks

Support InPlaceUpdate deployment strategy #944

acumino opened this issue Oct 7, 2024 · 2 comments
Assignees
@acumino
Labels
area/open-source Open Source (community, enablement, contributions, conferences, CNCF, etc.) related kind/enhancement Enhancement, improvement, extension priority/2 Priority (lower number equals higher priority)

Comments

@acumino
Copy link
Member

acumino commented Oct 7, 2024 •
edited
Loading

How to categorize this issue?

/area open-source
/kind enhancement
/priority 2

What would you like to be added:
As of now, machine deployment provides two strategies called Recreate and RollingUpdate, we would like to have new strategy called InPlaceUpdate, with two flavors Auto and Manual which should work as follows -

InPlaceUpdate:

The following step will be performed for in-place update on the machine:

  • Mark the machine as unschedulable.
  • Drain the node.
  • Mark the machine as ready for an update using a set of labels/annotations.
  • Wait for an annotation/label indicating that the machine has been updated.
  • Once the update is detected move the machine to the new machine set.
  • Uncordon the node successfully updated and moved to the new machine set.

Auto:

Machines will be selected based on maxUnavailable and will go through the steps mentioned above.

Manual:

Machines/nodes will be selected for updates based on certain labels, which the user has control over. This strategy gives users the flexibility to specify which machines/nodes should be updated by applying predefined labels. Once a machine is labeled, it will follow the same steps as the InPlace update.

Tasks
@acumino acumino added the kind/enhancement Enhancement, improvement, extension label Oct 7, 2024
@gardener-robot gardener-robot added area/open-source Open Source (community, enablement, contributions, conferences, CNCF, etc.) related priority/2 Priority (lower number equals higher priority) labels Oct 7, 2024
@acumino
Copy link
Member Author

acumino commented Jan 15, 2025

/assign @acumino @ary1992 @shafeeqes

@acumino
Copy link
Member Author

acumino commented Jan 15, 2025

/assign @ary1992

@acumino acumino changed the title Support InPlace and OnLabel deployment strategy Support InPlaceUpdate deployment strategy Jan 15, 2025
@acumino acumino mentioned this issue Jan 15, 2025
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@acumino acumino

Labels
area/open-source Open Source (community, enablement, contributions, conferences, CNCF, etc.) related kind/enhancement Enhancement, improvement, extension priority/2 Priority (lower number equals higher priority)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@acumino @gardener-robot