routing.http2.enabled does not work

[eddycharly]

Setting routing.http2.enabled=false in the alb attributes annotation does not work correctly.
Sometimes i set it to true, and the alb has http2 disabled.
Sometimes i set it to false, and the alb has http2 enabled.

In any case, when i succeed to set it to false, http2 is disabled for a few minutes and is reactivated a few minutes later.

Maybe a sort of cache issue...

Below are the controller logs, notice how it is reset to true after a while though i didn't change the ingress annotations :

I1101 18:55:12.539522       1 attributes.go:144] ingress/internet: Modifying ELBV2 attributes to [{    Key: "routing.http2.enabled",    Value: "true"  }].
I1101 19:23:09.220610       1 attributes.go:144] ingress/internet: Modifying ELBV2 attributes to [{    Key: "routing.http2.enabled",    Value: "false"  }].
I1101 19:55:10.642617       1 attributes.go:144] ingress/internet: Modifying ELBV2 attributes to [{    Key: "routing.http2.enabled",    Value: "true"  }].
I1101 20:42:08.725861       1 attributes.go:144] ingress/internet: Modifying ELBV2 attributes to [{    Key: "routing.http2.enabled",    Value: "false"  }].
I1101 20:55:12.355644       1 attributes.go:144] ingress/internet: Modifying ELBV2 attributes to [{    Key: "routing.http2.enabled",    Value: "true"  }].

[eddycharly]

/kind bug

[eddycharly]

/woof

[k8s-ci-robot]

@eddycharly:

In response to this:

/woof

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[gws]

This is happening consistently to me as well, using v1.1.4, but with a different annotation.

When I first set the annotation alb.ingress.kubernetes.io/load-balancer-attributes: idle_timeout.timeout_seconds=300, nothing happened.

Later, I set alb.ingress.kubernetes.io/load-balancer-attributes: idle_timeout.timeout_seconds=360 (note the different timeout value), and the following was logged by the controller:

Modifying ELBV2 attributes to [{    Key: "idle_timeout.timeout_seconds",    Value: "300"  }].

I then set alb.ingress.kubernetes.io/load-balancer-attributes: idle_timeout.timeout_seconds=300 once more and the following was logged:

Modifying ELBV2 attributes to [{    Key: "idle_timeout.timeout_seconds",    Value: "360"  }].

Further testing yielded the same results - the previous set of attributes are getting synced, not the current set of attributes.

[fejta-bot]

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

[fejta-bot]

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

[fejta-bot]

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

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

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

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.