aws-load-balancer-controller
aws-load-balancer-controller copied to clipboard
A Kubernetes controller for Elastic Load Balancers
I'm using nginx-ingress and want to expose gitlab-shell service on TCP port 22. ``` defaultBackend: enabled: false tcp: 22: gitlab/gitlab-gitlab-shell:22 config: server-tokens: false use-proxy-protocol: true service: type: "LoadBalancer" annotations: service.beta.kubernetes.io/aws-load-balancer-type:...
**Describe the bug** I have a configuration when the Load Balancer already exists and I just want ALBC to lookup this Network Load Balancer and configure the connection with the...
**Describe the bug** Self-signed certs deployed by this chart are missing the `issuerRef.group` and fail to renew in specific environments with the following error `Unknown issuer kind: Issuer` **Steps to...
**Describe the bug** OIDC client secret is not being properly configured on ALB listener which cause 561 Authentication Error Via aws console, by manually unchecking *Use existing client secret* and...
in values.yaml there is trailing whitespace in this line https://github.com/kubernetes-sigs/aws-load-balancer-controller/blob/f39ae43121c3f4de0129dda483c10b17a687491d/helm/aws-load-balancer-controller/values.yaml#L285 please force removal of trailing whitespace to make it easier to diff
**Describe the bug** Our setup uses OIDC authentication with IngressGroup. The auth action does not get attached to the LoadBalancer Rule unless we add OIDC-related annotations to the corresponding ingress....
### Issue The format of the table in https://github.com/kubernetes-sigs/aws-load-balancer-controller/blob/main/helm/aws-load-balancer-controller/README.md#configuration is broken half way through. ### Description This fixes the table formatting by making the necessary white space changes. You can...
### Description - added httproute matching logic - added precedence order logic to assign priority - added weighted target group support - sourceIp is not cover in this PR ->...
**Bug Description** If you enable external-dns's gateway sources, it is supposed to look at the HTTPRoute for hostnames and then create the DNS records pointing at the parent gateway. However,...
In [Guide > TargetGroupBinding > Specification > NetworkingIngressRule](https://kubernetes-sigs.github.io/aws-load-balancer-controller/v2.13/guide/targetgroupbinding/spec/#elbv2.k8s.aws/v1beta1.NetworkingIngressRule), it says: > If ports is empty or unspecified, it defaults to all ports with TCP. This does not appear to be...