-
Notifications
You must be signed in to change notification settings - Fork 579
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
Finalizers added after first read operation on AWS in AWSMachines #2601
Conversation
Need to update the tests appropriately, as the logic has changed. |
/lgtm /assign @sedefsavas for another set of 👁️ and approval |
One problem might be: this does not solve the case where the credentials were valid initially (the first findInstance() call succeeded), then for example it expired. I don't think there is an easy solution for this. |
No probably not. I don't think there's much more we can do here without modelling a more complex state machine. It at least unblocks the most trivial use case. |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sedefsavas 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:
Update finalizer addition logic for AWSMachine. If we apply AWS workload cluster yaml with invalid credentials, then AWSMachine object is created and stuck because of invalid credentials. Once we try to delete that yaml, AWSMachine object stuck. So adding finalizer in AWSMachine only after first successful AWS read operation.
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 #2270
Special notes for your reviewer:
With this change AWSMachine object is deleted in case of invalid credentials, same needs to be done for AWSCluster. WIP because AWSCluster finalizer updation requires a bit of refactoring in reconciliation logic
Checklist:
Release note: