-
**Describe the bug**
My purpose is creating some additional NLB listener on port 22 on an NLB created by AWS LB ingress controller.
I'm using `external-managed-tags` configuration to avoid reconcili…
-
I am migrating in-tree LB controller to AWS Loadbalancer controller, and this controller requires annotation to create public-facing NLB otherwise internal is not consistent in behavior with the old C…
-
CloudFormation already supports it and properties are similar to ALB. We need to think about `barcelona.yml` structure
-
```
when I deploy ELMAH on a NLB environment, I browse elmah.axd can only show
error on one dedicated host
web administators can view all error in one place on a NLB environment
```
Original issue…
-
```
when I deploy ELMAH on a NLB environment, I browse elmah.axd can only show
error on one dedicated host
web administators can view all error in one place on a NLB environment
```
Original issue…
-
```
when I deploy ELMAH on a NLB environment, I browse elmah.axd can only show
error on one dedicated host
web administators can view all error in one place on a NLB environment
```
Original issue…
-
### Describe the feature
AWS Network Load Balancer now supports configurable TCP idle timeout.
Announcement: https://aws.amazon.com/about-aws/whats-new/2024/09/aws-network-load-balancer-tcp-idle…
-
This seems to be because of `service.beta.kubernetes.io/aws-load-balancer-nlb-target-type](http://service.beta.kubernetes.io/aws-load-balancer-nlb-target-type=ip`.
We have this because using `NodePor…
-
```
when I deploy ELMAH on a NLB environment, I browse elmah.axd can only show
error on one dedicated host
web administators can view all error in one place on a NLB environment
```
Original issue…
-
```
when I deploy ELMAH on a NLB environment, I browse elmah.axd can only show
error on one dedicated host
web administators can view all error in one place on a NLB environment
```
Original issue…