alibaba/alibaba-load-balancer-controller

Alibaba Load Balancer Controller

Alibaba Load Balancer Controller is a cloud-native controller that allows you to use ALB (Application Load Balancer) and NLB (Network Load Balancer) in self-managed Kubernetes clusters.

• An AlbConfig object is a CustomResourceDefinition (CRD) used to configure ALB instances and listeners. An AlbConfig object corresponds to one ALB instance.
• An Ingress contains reverse proxy rules. It controls to which Services HTTP or HTTPS requests are routed. For example, an Ingress routes requests to different Services based on the hosts and URLs in the requests.
• An AlbConfig object is used to configure an ALB instance. The ALB instance can be specified in forwarding rules of multiple Ingresses. Therefore, an AlbConfig object can be associated with multiple Ingresses.
• Use Service annotations config NLB instance, listeners, and backend server groups. provides ultrahigh performance and auto scaling.

Start

• Deployment
• Quick start
• ALB Usage
• NLB Usage

Development

• Perform e2e tests on existing staging scenarios to make sure that the features are working as expected. make test
• Build application images for Kubernetes clusters. make image

Communication

• For more information about ALB features, see Official documentation.

• For more information about NLB features, see Official documentation.

• If you have questions, submit issues.

alibaba-load-balancer-controller's Issues

两条ingress转发相同的svc地址会创建重复的服务器组，能不能复用？

我创建了两条ingress规则，不同的域名指向同一个svc地址

比如：

apiVersion: networking.k8s.io/v1
 kind: Ingress
 metadata:
   name: demo-https-1
   namespace: default
 spec:
   ingressClassName: alb
   tls:
   - hosts:
     - demo.alb.ingress.top
   rules:
     - host: demo.alb.ingress.top
       http:
         paths:
           - backend:
               service:
                 name: demo-slb-in
                 port:  
                   number: 9080
             path: /
             pathType: Prefix

apiVersion: networking.k8s.io/v1
 kind: Ingress
 metadata:
   name: demo-https-2
   namespace: default
 spec:
   ingressClassName: alb
   tls:
   - hosts:
     - demo2.alb.ingress.top
   rules:
     - host: demo2.alb.ingress.top
       http:
         paths:
           - backend:
               service:
                 name: demo-slb-in
                 port:  
                   number: 9080
             path: /
             pathType: Prefix

事实上会生成两个名字相同的服务器组，有没有可以复用同一个服务器组的配置？

请问如何使用cert-manager管理的证书？

看文档只有关联阿里云官方数字证书的内容，如果使用cert-manager生成的证书如何关联ALB呢？

如何在资源清单中配置ALB的转发规则呢？

比如按照header和请求路径进行转发等功能，在ALB的文档中没有看到配置的例子。

ListenerId is mandatory for this action

Apply requestTimeout to an exists albconfig caused "Message: ListenerId is mandatory for this action" error.

Thanks.

Do we support access control on alb with load-balance-controller?

Just like the title says that we want to add some access control for different listeners, and we know that the ALB is supported the access control by default, but I can't find the related features of the alb ingress, please confirm that wherther can support the access control with controller.