Open nueavv opened 2 weeks ago
This issue is currently awaiting triage.
If CAPA/CAPI contributors determines this is a relevant issue, they will accept it by applying the triage/accepted
label and provide further guidance.
The triage/accepted
label can be added by org members by writing /triage accepted
in a comment.
The issue appears to be caused by the value field in the taint having an empty string. The taint configuration is as follows:
This empty string in the value field might be leading to the observed behavior.
/kind bug
What steps did you take and what happened: While managing an EKS cluster using AWSManagedMachinePool, a panic error occurs when trying to delete a taint after adding it. Below are the related log messages.
Initial Error Log
Updated Error Log
What did you expect to happen: Taints should be deleted without causing a panic error.
Anything else you would like to add:
Current
TaintsFromSDK
function implementation:Suggestions:
Resolve the panic error that occurs during taint deletion. When the taint array is empty, ensure that existing taints are deleted. Review the logic handling empty taint arrays and nil fields.
Environment:
Cluster-api-provider-aws version: [version] 2.5.0 Kubernetes version: (use kubectl version): [version] 1.25.5 on local kubernetes OS (e.g. from /etc/os-release): [version] ubuntu 20.04