Closed t0rr3sp3dr0 closed 4 years ago
I can confirm this behavior. Tags are properly applied to TargetGroups, however.
waf-acl-id is also experiencing similar behavior. Adding the annotation to an existing ingress doesnt do anything. removing the annotation causes the ingress controller to add the waf acl to the alb. I believe that the ingress controller's sync period will eventually reconcile the proper behavior, but this defaults to 1 hour.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen
.
Mark the issue as fresh with /remove-lifecycle rotten
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /close
@fejta-bot: Closing this issue.
I have the same issue and it's not being fixed
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen
.
Mark the issue as fresh with /remove-lifecycle rotten
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /close
@fejta-bot: Closing this issue.
/reopen
Well, I tried
@swarmer: You can't reopen an issue/PR unless you authored it or you are a collaborator.
/reopen
@t0rr3sp3dr0: Reopened this issue.
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen
.
Mark the issue as fresh with /remove-lifecycle rotten
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /close
@fejta-bot: Closing this issue.
Any update on this issue ? Even I am facing same issue while enabling logs on alb.
@tibin-mfl: You can't reopen an issue/PR unless you authored it or you are a collaborator.
Just ran into the exact same issue trying to update alb.ingress.kubernetes.io/load-balancer-attributes
.
Also seeing the problem with alb.ingress.kubernetes.io/load-balancer-attributes
.
ALB Ingress Controller v1.1.8, Kubernetes v1.17.
If you update
alb.ingress.kubernetes.io/tags
, tags are not created, deleted, or updated on ELB. For it to update you need to changealb.ingress.kubernetes.io/tags
again, and it will show the previous tags. Then you change it again and the tags from the second application will appear, but not the ones from the last application.The AWS tags are always one state behind from the ones specified on Kubernetes YAML.
It is even stranger because
AddTags
andDeleteTags
events are logged on CloudTrail and on AWS search bar I can see the tags and its values, but if I filter no ELBs are listed. The same happens on AWS CLI and Boto3 if you describe the ELBs, its tags do not appear or appear outdated.I've waited more than 10min to verify if there was some delay on tag application but nothing happened. The tags just update if I change Ingress YAML again.
The changes on YAML doesn't necessarily need to be on
alb.ingress.kubernetes.io/tags
, any change the forces Kubernetes to reconfigure Ingress will make the tags from the previous configuration appear.