Kamalpreet-KK
Results
1
comments of
Kamalpreet-KK
> Just had this occur on one of our EKS 1.28 clusters, fixed it by: > > * Look at the node group node list to get current instance names...