Fix for #7450 sigsegv error when trying to clean up the stacks with missing eks cluster #7731
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.
Description
This PR is to fix the issue #7450 encountered when using
eksctl delete cluster --force
command to delete the stacks after manually deleting the eks cluster resource.When a cluster is inoperable (clusterOperable=false), the
c.ctl.Status.ClusterInfo
value isnil
, and therefore passingc.ctl.Status.ClusterInfo.Cluster
to theNewTasksToDeleteClusterWithNodeGroups
function (owned.go#L138) is causing the nil pointer exception.I'm setting the
c.ctl.Status.ClusterInfo
to an empty struct so that the function signature is respected. The actual value is never used in the function anyway because ofclusterOperable=false
.Checklist
README.md
, or theuserdocs
directory)area/nodegroup
) and kind (e.g.kind/improvement
)BONUS POINTS checklist: complete for good vibes and maybe prizes?! 🤯