Release a Non-Critical Update in Managed Instance Group without Impacting Running Instances

How to Update Managed Instance Group with New Instance Template

Question

You have developed a non-critical update to your application that is running in a managed instance group, and have created a new instance template with the update that you want to release.

To prevent any possible impact to the application, you don't want to update any running instances.

You want any new instances that are created by the managed instance group to contain the new update.

What should you do?

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D.

C.

Based on the scenario described, the goal is to release a non-critical update to an application running in a managed instance group without impacting any currently running instances. Instead, the goal is to have any new instances created by the managed instance group contain the new update.

Option A, starting a new rolling restart operation, would restart all the instances in the managed instance group, including the currently running ones, which is not desired in this scenario. Therefore, Option A is not the correct answer.

Option B, starting a new rolling replace operation, would replace all the instances in the managed instance group with new ones that have the new update, but again, this is not desired as the currently running instances are not impacted. Therefore, Option B is not the correct answer.

Option C, starting a new rolling update and selecting the Proactive update mode, would allow the managed instance group to create new instances with the new update, while not impacting any currently running instances. The Proactive update mode ensures that new instances are created with the new update before the old ones are replaced, allowing for a smooth transition. Therefore, Option C is the correct answer.

Option D, starting a new rolling update and selecting the Opportunistic update mode, would allow the managed instance group to replace any currently running instances with new ones that have the new update when there is capacity available. This is not desired in this scenario, as the goal is to avoid impacting any currently running instances. Therefore, Option D is not the correct answer.

In summary, the correct answer to the scenario described is Option C: start a new rolling update and select the Proactive update mode.