fix: Fix retrieving NodePool when rolling back to v0.31.x #5621
+1
−8
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #5613
Description
This fixes an issue where a user has deployed a NodeClaim to their cluster with a Node and a NodeClaim that has entered a terminating state. This ensures that we don't try to retrieve the parent NodePool information for the Node when we are getting the node from the CloudProvider.
How was this change tested?
make apply
and validate rollback scenarioDoes this change impact docs?
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.