-
Notifications
You must be signed in to change notification settings - Fork 560
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
Improve AWSMachinePool diff to default to existing values when comparing launch templates #4378
Improve AWSMachinePool diff to default to existing values when comparing launch templates #4378
Conversation
…ing launch templates
Hi @cnmcavoy. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/ok-to-test |
{ | ||
mixedInstancesPolicy := machinePoolScope.AWSMachinePool.Spec.MixedInstancesPolicy | ||
// InstancesDistribution is optional, and the default values come from AWS, so | ||
// they are not set by the AWSMachinePool defaulting webhook. If InstancesDistribution is |
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.
have we considered to default the API explicitly?
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.
Is this only happening with InstancesDistribution?
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.
We could default in the webhook, but the default types for some of the fields are not available as types in CAPA, so that would turn this bugfix into an API change. See the discussion here: #4194 (comment)
/lgtm |
/approve Thanks for your patience and tenacity, @cnmcavoy! 🙏 |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dlipovetsky The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind bug
What this PR does / why we need it:
Changes how the AWSMachinePool and ASG retrieved from AWS is compared, so that we copy the existing AWSMachinePool values, and compare only fields we manage. This fixes bugs around partially set fields (e.g ,
MixedInstancesPolicy
is set with an instance distribution, but no mixed instance policy) where the AWS defaults do not match the zero-values of fields.Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #4070
Special notes for your reviewer:
Split off from #4194
Checklist:
Release note: