Azure: Changing instance type post deployment

[#1]

I'm using Altus Director 6.2. 

Is the following declaration in your latest Aluts Director documentation still accurate?

Changing the Instance Type is Not Supported in Azure

• Changing the instance type of an already-deployed VM is not supported in Azure.
• Changing the instance type of a VM through a tool external to Altus Director is not supported in Azure. You cannot, for example, use the Azure Portal to change the instance type. Altus Director is not updated when instance type changes are made with external tools, and your cluster will show errors in Altus Director.

I have performed both of the actions described in the bullet points above after we decided our existing workers were not sized properly for the amount of data being ingested / processed.   Cloudera Director still shows the cluster in a "green" state.  No complaints / errors / warnings thus far.   Is this really not supported?

Reference: https://www.cloudera.com/documentation/director/latest/topics/director_get_started_azure_important_n...

[#2 · Accepted solution]

It looks like we failed to update the documentation when we added support for this in 6.2.0. Good catch!

The cluster refresher should detect changes to the instance type made in the Azure portal and update the cluster template with the new information. If this results in an instance group being inconsistent (with some instances on the old instance type and some on the new), grow operations will be blocked for the cluster. If the instance group is made consistent (by either changing all the instances to the new instance type, or by shrinking away instances using the old instance type), grow will be enabled, and a subsequent grow operation will use the new instance type.

[#3]

Thank you for the clarification.   

D.