Upgrading from 2.8.3 to 2.11.0 triggers changes in listener rules.

[kashya2]

I am trying to update aws-load-balancer-controller from v2.8.3 to v2.11.0, upgrade is smooth but as soon as pods with new version is deployed, I see all the listener attributes for ALB changes with below messages, but confirmed there is nothing that actually changes, but there are entries in cloudtrail as well, mentioning there was ModifyRule event happend.

{"level":"info","ts":"<timestamp>","logger":"controllers.ingress","msg":"modified listener rule","stackID":"stackId","resourceID":"443:28","arn":"<ListenerARN>"}

• Can someone confirm on what are these changes is it related to listenerAttributes support added in v2.10.1 or something else?

[shraddhabang]

I don't think updating the listener attributes should result in modifying the listener rules as long as there is no changes done to the rules on ingress. I think the reason could be something else. Did you update rules by any chance?

[kashya2]

Actually there were no rule changes and we just upgraded from version v2.8.3 to v2.11.0 and as soon as new version pod is deployed it triggers rules changes but again there are no actual changes in rules, but somehow in logs it shows "Modified Listener rule"

[kashya2]

We tried this in another environment and its same behaviour there as well, this time we exported the listener rules before the upgrade and did the upgrade (modified listener rules was triggered) and compared with the latest listener rules and it was same.
Also thought of configuring AWS Config to confirm the changes but listener rules are not supported as of now.

[s-marinkovic]

Hi @shraddhabang ,

I have the same issue as @kashya2 described. Updated aws-load-balancer-controller from v2.9.1 to v2.11.0 and in the logs i see the ModifyRule events with following error:
api error ValidationError: A rule can only have '5' condition values

My questions are:

• Why there is ModifyRule event
• Why there is error even I've checked all our rules have 5 or less condition values

Can you please check this, because we won't rollout update to our other environments until this issue is present.

Update:

We had in different configuration update of conditions and it had indeed more than 5 values in total. So there is no issue with 2.11.0 .

[kashya2]

Any updates on this, tested again and got same results.