-
Notifications
You must be signed in to change notification settings - Fork 26
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.
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
Use zone-info while scaling-up the node-group from zero #38
Use zone-info while scaling-up the node-group from zero #38
Conversation
@@ -946,6 +946,7 @@ type AzureVirtualMachineProperties struct { | |||
OsProfile AzureOSProfile | |||
NetworkProfile AzureNetworkProfile | |||
AvailabilitySet AzureSubResource | |||
Zone *int |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a workaround for now.
We should ideally re-vendor the MCM, but it seems challenging due to recently updated Azure-dependencies in MCM, I would prefer to do it separately.
@@ -424,15 +428,19 @@ func (m *McmManager) GetMachineDeploymentNodeTemplate(machinedeployment *Machine | |||
GPU: azureInstance.GPU, | |||
} | |||
region = mc.Spec.Location | |||
if mc.Spec.Properties.Zone != nil { | |||
// Do not re-use the zone before re-vendoring mcm. | |||
zone = mc.Spec.Location + strconv.Itoa(*mc.Spec.Properties.Zone) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yet to test this change for Azure.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tested this PR with Azure now, works well.
What this PR does / why we need it: This PR uses the zone-information for scaling the node-groups from zero.
Which issue(s) this PR fixes:
Fixes #34
Special notes for your reviewer:
Release note: