Paul "TBBle" Hampson

The failure log came from an update. I assume you added the port during the update operation? I'm wondering if the AWS Load Balancer Controller somehow saw the updated structure...

Also, quick note, it looks like your rebase has ended up with an empty-commit duplicate of 9b3880fffc2680460436ff4bd462640a7bdc03b1 (see f78cf1e57e09a1965511a6ae0ab4c90c82f132ad)

[Mixed-protocol (TCP/UDP) Service is alpha in k8s 1.20](https://kubernetes.io/docs/concepts/services-networking/service/#load-balancers-with-mixed-protocol-types), is this the feature ticket to track for support for the `MixedProtocolLBService` feature gate? Or is this for multiple Services contributing to...

I assume you meant @kishorj with that question. [Per the docs](https://docs.aws.amazon.com/elasticloadbalancing/latest/network/load-balancer-listeners.html), `TCP_UDP` is explicitly for the "same port in TCP and UDP" case. > To support both TCP and UDP...

/remove-lifecycle stale

/remove-lifecycle stale

Assuming you're asking about https://github.com/kubernetes-sigs/aws-load-balancer-controller/issues/1608#issuecomment-937346660, the TCP support is for HTTP/1 and HTTP/2. As of July 2022 [according to Wikipedia](https://en.wikipedia.org/wiki/HTTP/3) only 75% of web browsers support HTTP/3, so not also...

If I'm following correctly, landing #773 would be sufficient for Cluster Autoscaler to operate correctly with `--balancing-ignore-label=topology.ebs.csi.aws.com/zone`, because #773 is ensuring that it has the same value as `topology.kubernetes.io/zone`. So...

To cross-link, it seems there's [a problem with this approach](https://github.com/kubernetes-sigs/aws-ebs-csi-driver/issues/675#issuecomment-971939569). I'm not yet clear on the actual blocker there, unless there's a need/use-case for topology zones that do not match...

`AWS_SDK_LOAD_CONFIG` is effectively set by default, as of #201 (merged in February 2020), which will be part of the next release.