You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because of how the CCM selects a Load Balancer security group by using the
"kubernetes.io/cluster/<infraID>: owned" tag, CAPA removes that tag from
all the other security groups [1].
That means that when the Installer is looking for resources to delete
with that tag, it will never find those security groups and they'll stay
behind. To avoid that, let's also search for resources with the
"sigs.k8s.io/cluster-api-provider-aws/cluster/<infraID>: owned" tag
during cluster destroy.
[1] kubernetes-sigs/cluster-api-provider-aws#4571
0 commit comments