PCP-3797: Added nil pointer check before dereferencing Nodegroup version #956
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.
Added a check to ensure that the nodegroup version is not nil before dereferencing it.
What type of PR is this?
/kind bug
What this PR does / why we need it:
This PR adds a nil pointer check for the nodegroup version in the reconcileNodegroupVersion function. This prevents potential runtime panics caused by dereferencing a nil pointer when the nodegroup version is not set during AWSManagedMachinePool reconciliation .
Example: When the nodegroup status in in "CREATE_FAILED" state due to unsupported AWS Launch template in Palette then the nodegroup version is nil and we encounter panic calls.
Which issue(s) this PR fixes:
Fixes https://spectrocloud.atlassian.net/browse/PCP-3797
Upstream fix : kubernetes-sigs#5019