Controller not cleaning up old resources #3783
Labels
kind/bug
Categorizes issue or PR as related to a bug.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
Describe the bug
I initially created 3 ingresses with 3 ALBs as I was unaware I could use the
group.name
annotation to share 1 ALB. I am now combing all ingresses to use the same group to save money. I now have 1 ALB that works as expected for all 3 ingresses. However, my old ALBs, TargetGroups, SecurityGroups and TargetGroupBinding(k8s) are still there. They technically aren't being used bc DNS doesn't point to them, but I would expect those to get cleaned up. Not sure if I did something wrong or am missing a setting. I do not see any logs in the controller pod indicating it's even trying to cleanup these resources. I thought maybe it could be a permissions issue, but I think I'd see some type of error in the logs. Additionally, I don't see any k8s events indication issues like failure to delete the TargetGroupBinding, I don't think it's even trying to delete it. Thanks for the help.Steps to reproduce
group.name
annotation to be in the same groupExpected outcome
Only the group ALB exist and deprecated ALBs, TargetGroups, SecurityGroups and TargetGroupBindings are cleaned up.
Environment
2.8
1.29
yes, eks.7
Additional Context:
Deploying controller via helm. v1.8.1
The text was updated successfully, but these errors were encountered: