Default tags don't get applied to previously created "backend" security group

[romich]

Describe the bug Tags from --default-tags argument don't get applied to previously created "backend" security group.

Steps to reproduce

1. Deploy chart with minimal config.
2. Create at least 1 ALB Ingress.
3. Update chart, providing defaultTags option.
4. Observe default tags only on frontend security group.

Expected outcome Both frontend and backend security groups get provided tags.

Environment

• AWS Load Balancer controller version: v2.4.4
• EKS version: v1.23.10-eks-15b7512

Additional Context: n/a

[kishorj]

/kind feature @romich, Thanks for letting us know, we will fix it in a patch release. Currently the tags are applied only during backend SG creation.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[Hokwang]

/remove-lifecycle stale