Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question about tagging listeners rules in ALB #3973

Open
fabgaubert opened this issue Dec 10, 2024 · 3 comments
Open

Question about tagging listeners rules in ALB #3973

fabgaubert opened this issue Dec 10, 2024 · 3 comments
Assignees
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature.

Comments

@fabgaubert
Copy link

Hi,

Is it possible to add tags directly to ALB listeners rules instead of the ALB or its listeners?
I need to assign a unique tag to each rule created within the ALB.

Thank you in advance for your help.

Best regards,

@shraddhabang
Copy link
Collaborator

Hello @fabgaubert , Unfortunately we currently don't support tagging each rule with unique tags yet. We will mark this as feature request. This can be a good first issue. We welcome any community contributions for this.

@shraddhabang shraddhabang added kind/feature Categorizes issue or PR as related to a new feature. good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. labels Dec 10, 2024
@omerap12
Copy link
Member

/assign

@omerap12
Copy link
Member

Hello @fabgaubert , Unfortunately we currently don't support tagging each rule with unique tags yet. We will mark this as feature request. This can be a good first issue. We welcome any community contributions for this.

To clarify, I’m considering adding a new annotation for this purpose since the rules field in the Ingress API spec is part of Kubernetes’ core API and can’t be modified directly to include custom fields. Here's an example of what I have in mind:

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  annotations:
    alb.ingress.kubernetes.io/rule-tags: |
      {
        "example.com:/api": {
          "team": "backend",
          "cost-center": "123"
        },
        "/docs": {
          "team": "docs",
          "cost-center": "456"
        }
      }
spec:
  rules:
    - host: example.com
      http:
        paths:
          - path: /api
            pathType: Prefix
            backend:
              service:
                name: api-svc
                port:
                  number: 80
    - http:
        paths:
          - path: /docs
            pathType: Prefix
            backend:
              service:
                name: docs-svc
                port:
                  number: 80

what do you think?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

3 participants