-
Notifications
You must be signed in to change notification settings - Fork 24
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
Sync with upstream v1.29.4
#327
Conversation
… to drainability rules
…lity Convert scale-down checks to drainability rules
Update ec2_instance_types with make generate
- HasNodeGroupStartedScaleUp checks wheter a scale up request exists without checking any upcoming nodes.
Add HasNodeGroupStartedScaleUp to cluster state registry.
jbartosik et al are transitioning off of workload autoscalers (incl vpa and addon-resizer). kwiesmueller is on the new team and has agreed to take on reviewer/approver responsibilities.
Add kwiesmueller to OWNERS
…-fix Add information about provisioning-class-name annotation.
Fix multiple run of informers created in fetcher.go
…on't create secret Signed-off-by: Jonathan Raymond <[email protected]>
Signed-off-by: Jonathan Raymond <[email protected]>
Add mechanism to override drainability status
Initialize default drainability rules
…scale from zero method via environment variable The architecture label in the build generic labels method of the cluster API (CAPI) provider is now populated using the GetDefaultScaleFromZeroArchitecture().Name() method. The method allows CAPI users deploying the cluster-autoscaler to define the default architecture to be used by the cluster-autoscaler for scale up from zero via the env var CAPI_SCALE_ZERO_DEFAULT_ARCH. Amd64 is kept as a fallback for historical reasons. The introduced changes will not take into account the case of nodes heterogeneous in architecture. The labels generation to infer properties like the cpu architecture from the node groups' features should be considered as a CAPI provider specific implementation.
|
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.
Looks good in general
In addition to the two changes asked, I have one question, and one more change
- Do we not update
SYNC-CHANGES
with patch versions? - Can you please update the docstring of
machine_cloud_provider.GetOptions
to the new docstring here
cluster-autoscaler/main.go
Outdated
// FORK-CHANGE: logging version of g/autoscaler as well | ||
gardenerversion, err := os.ReadFile("VERSION") | ||
if err != nil { | ||
klog.Warningf("Error reading gardener autoscaler version, err: %s", err) | ||
} else { | ||
klog.V(1).Infof("Gardener Cluster Autoscaler %s", gardenerversion) | ||
} | ||
|
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 removed by error ig. Can you please re add this?
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.
Did not remove it by mistake. There is no Version
file anymore. So we can either add a version file and then reintroduce this or we can get rid of this.
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 checked and it is working fine. It uses the VERSION file at the root of the repo, not the version dir. I have added this piece of code back
It is not needed IMO as the sync changes are for minor and not patch versions.
The docstring is part of 1.30 and is also not present upstream. I think it is fine for us to keep it like this. |
Okay, fair enough for me then |
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.
Thanks for the changes
/lgtm
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #326
Special notes for your reviewer:
IT pass for AWS
Release note: