You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
With current chart, It is not possible to setup ssl-redirect for aws loadbalancer controller ingress.
Describe the solution you'd like
Adding a extraPath map value to each hosts. Where serverName and servicePort can be defined will resolve this issue.
Values will look like
ingress:
enabled: trueannotations:
alb.ingress.kubernetes.io/actions.ssl-redirect: '{"Type": "redirect", "RedirectConfig": { "Protocol": "HTTPS", "Port": "443", "StatusCode": "HTTP_301"}}'alb.ingress.kubernetes.io/certificate-arn: ACM ARNalb.ingress.kubernetes.io/listen-ports: '[{"HTTP": 80}, {"HTTPS":443}]'alb.ingress.kubernetes.io/scheme: internet-facingalb.ingress.kubernetes.io/target-type: instancekubernetes.io/ingress.class: alb# Provide an array of values for the ingress host mappinghosts:
- athens-proxy.hostextraPaths:
# This will be added to each hosts
- service: ssl-redirectport: use-annotationpath: /*
I noticed I missed the detail about the default path.
On nginx / will match all paths, But on ALB it uses glob match, so it needs /* to match all paths.
Is your feature request related to a problem? Please describe.
With current chart, It is not possible to setup ssl-redirect for aws loadbalancer controller ingress.
Describe the solution you'd like
Adding a
extraPath
map value to each hosts. WhereserverName
andservicePort
can be defined will resolve this issue.Values will look like
ingress template will then
This is a method suggest by aws loadbalancer documentation
The text was updated successfully, but these errors were encountered: