[Feature Request ] Features for AWS ALB / NLB

[M00nF1sh]

Track features that need support from AWS ALB / NLB service before we can support them in this controller 😄

ALB

• [ ] Manipulate HTTP Request
  • https://github.com/kubernetes-sigs/aws-load-balancer-controller/issues/1268
• [ ] Manipulate HTTP Response
  • https://github.com/kubernetes-sigs/aws-load-balancer-controller/issues/1454
  • https://github.com/kubernetes-sigs/aws-load-balancer-controller/issues/1397
• [ ] Server-side retry
  • https://github.com/kubernetes-sigs/aws-load-balancer-controller/issues/1447
• [ ] Fix OIDC scope
  • https://github.com/kubernetes-sigs/aws-load-balancer-controller/issues/1344
• [ ] ALB support GZIP compression
  • https://github.com/kubernetes-sigs/aws-load-balancer-controller/issues/1132
• [ ] ALB support regex path
  • https://github.com/kubernetes-sigs/aws-load-balancer-controller/issues/1760
• [ ] ALB support HTTP healthcheck for GRPC backends
  • https://github.com/kubernetes-sigs/aws-load-balancer-controller/issues/1883
• [ ] ALB support for mutual TLS and passing client cert
  • https://github.com/kubernetes-sigs/aws-load-balancer-controller/issues/1973
• [ ] ALB support for rate limit
  • https://github.com/kubernetes-sigs/aws-load-balancer-controller/issues/2722
• [ ] 308 redirection
  • https://github.com/kubernetes-sigs/aws-load-balancer-controller/issues/2654

NLB

• [ ] NLB support for SecurityGroups

[fejta-bot]

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale

[ffoysal]

any ETA on such a important feature?

[yuliyantsvetkov]

Any ETA here, guys ? Its the 21st century !

[M00nF1sh]

@ffoysal @yuliyantsvetkov the latest ETA i got from ELB team for request manipulation is Q2 2022.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[kc-sn]

@M00nF1sh is there anywhere we can track the upstream issues on the AWS side for these features?

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[adawalli]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[itskingori]

/remove-lifecycle stale

[hyerim-gn]

@ffoysal @yuliyantsvetkov the latest ETA i got from ELB team for request manipulation is Q2 2022.

Are there any updates?

[anthonyliriano]

Is the HTTP Request Header manipulation still being considered?

[neerajjain92]

Any update on this ?

[doctornkz]

Waiting Rate Limit feature for ALB, WAF too slow to help out with spike-loads.

[futurelm]

bro, it is Oct, where is Q2 2022?

[dejwsz]

bro, it is Oct, where is Q2 2022?

you know - they store so much data so relativistic time dilation appeared ;)

[or-navon]

Any progress with setting response headers?

[evyros]

Still waiting...

[nuwansa]

badly need this.....

[johngmyers]

This is a tracking issue for features needed from an upstream project. Querying the status of those features here is less than productive. Such queries should be directed to the upstream project.

[antonyfray]

This is a tracking issue for features needed from an upstream project. Querying the status of those features here is less than productive. Such queries should be directed to the upstream project.

Would you mind directing us to the upstream project in question please?

[johngmyers]

The upstream project would be AWS Elastic Load Balancing.

[edijsdrezovs]

Is the HTTP Request Header manipulation still being considered?

Any ETA on this?

[DariusX]

As @johngmyers mentioned above, there really cannot be an ETA on this project, because this project uses features available on AWS ELB. If AWS ELB does not support a feature, then this project cannot do so either.

I think the thing that folks who have experience with NGNIX style ingress do not realize that this is quite different. (I too had the same confusion when I first used this project.) With something like NGNIX, it is doing the routing of incoming requests. That is not how this project works. With this project, all the work of handling requests is being done by AWS ELB, not by the pod deployed by this project. The job of this project is to take the Ingress config as defined in EKS, and automatically spin up and configure AWS ELB.

So, when asking for a feature, the first question is: is this feature something that is in AWS ELB? In other words, is it possible to configure AWS ELB manually, to do whatever is being requested. If the answer is "yes", then this project can definitely create an automated way to configure that feature. But, if AWS ELB cannot be configured to do what's being requested, then this project can't do anything about it, because this project does not actually DO Ingress, it only CONFIGURES ingress using AWS ALB.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[itskingori]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[acgs771126]

AWS NLB supported security group now, so when will aws-loadbalancer-controller can also support create NLB with sg by service? thanks.

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[asychev]

@acgs771126 AWS NLB does not support SGs