kubernetes-sigs/aws-load-balancer-controller

Merge ALB rules by the same host

Open

#2,678 opened on Jun 6, 2022

View on GitHubContributor guide
 (8 comments) (7 reactions) (0 assignees)Go (1,644 forks)auto 404
good first issuekind/featurelifecycle/stale

Repository metrics

Stars
 (4,317 stars)
PR merge metrics
 (PR metrics pending)

Description

Is your feature request related to a problem? We would like to be able to merge rules in the ingress resource, on the ALB level.

For example, when creating the following -

spec:
  rules:
    - http:
        paths:
          - path: /test1
            pathType: ImplementationSpecific
            backend:
              service:
                name: service_name
                port:
                  number: 80
          - path: /test2
            pathType: ImplementationSpecific
            backend:
              service:
                name: service_name
                port:
                  number: 80
    - http:
        paths:
          - path: /*
            pathType: ImplementationSpecific
            backend:
              service:
                name: service_name
                port:
                  number: 80

We want the controller to merge the two paths in the first rule, and create one rule in the ALB. We are aware of the conditions annotation, but unfortunately working with it dynamically is very complicated. Is there an easier way?

Contributor guide

Research direction
Explore the controller's ALB rule generation logic. Look at how ingress rules are converted into listener rules, particularly how conditions are built. Investigate whether paths with the same host are grouped before rule creation. Understand the current behavior and design an approach to merge rules with the same host.
Tech stack
gokubernetesaws
Domain
backendinfrastructure
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GitGoKubernetesAWS
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35