-
Notifications
You must be signed in to change notification settings - Fork 29
Add labels to BasicIgnoredLabels to fix similarity check #368
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
Add labels to BasicIgnoredLabels to fix similarity check #368
Conversation
| // LabelTopologyDiskCSIAzure is a CSI-specific label for disk driver in Azure. | ||
| LabelTopologyDiskCSIAzure = "topology.disk.csi.azure.com/zone" | ||
| // LabelAWSZoneID indicates the zone-id of the node in AWS | ||
| LabelAWSZoneID = "topology.k8s.aws/zone-id" |
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.
| LabelAWSZoneID = "topology.k8s.aws/zone-id" | |
| LabelTopologyAWSZoneID = "topology.k8s.aws/zone-id" |
Consider changing this var (feel free to use something different if you have more ideas) for uniformity as other labels around topology seem to follow it
| // LabelMachineName adds the name of the machine to the node | ||
| LabelMachineName = "node.gardener.cloud/machine-name" |
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.
Nit: Please move this label to be above all cloud provider labels
aaronfern
left a comment
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.
/lgtm
6e805c8
into
gardener:machine-controller-manager-provider
What this PR does / why we need it:
This PR fixes a bug which made CA treat similar node groups as dissimilar, resulting in imbalanced scale ups across zones. The PR adds the following labels to
BasicIgnoredLabels:The values for these labels will be ignored during the similarity check. Hence, two node templates with differing values for these labels can still be considered "similar" if other similarity checks pass.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Unit tests and integration tests (aws) passed.
Release note: