Aws-load-balancer-controller: ssl-redirect only when incoming port is 80 ?

Created on 29 Dec 2018 · 5Comments · Source: kubernetes-sigs/aws-load-balancer-controller

I have a situation where I have 2 https listen-ports defined and I want ssl redirect to 443 when the incoming request is http:80 .

I have the following annotations:

    alb.ingress.kubernetes.io/actions.redirect: '{"Type": "redirect", "RedirectConfig": { "Protocol": "HTTPS", "Port": "443", "StatusCode": "HTTP_301"}}'
    alb.ingress.kubernetes.io/listen-ports: '[{"HTTP": 80}, {"HTTPS": 443}, {"HTTPS": 8443} ]'

And the first rule is:

  rules:
  - http:
      paths:
      - backend:
          serviceName: redirect
          servicePort: use-annotation
        path: /*

I do NOT want the redirect action when the incoming port is 8443, but it is currently being added to that listener. Is there a way I can modify the actions.redirect annotation to only add the redirect rule on the http:80 listener and not the https:8443 listener ?

lifecyclrotten

Source

gigi-at-zymergen

👍1

Most helpful comment

hi, it's not supported for now since we cannot specify rules per listener port.
it will be supported after we added support for "ingress group"

M00nF1sh on 1 Jan 2019

👍3

All 5 comments

hi, it's not supported for now since we cannot specify rules per listener port.
it will be supported after we added support for "ingress group"

M00nF1sh on 1 Jan 2019

👍3

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

fejta-bot on 28 Apr 2019

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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 rotten

fejta-bot on 28 May 2019

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

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

fejta-bot on 27 Jun 2019

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

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

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.