Closed nitrocode closed 1 year ago
Describe the bug The ssl-redirect doesn't add a target group redirect. Instead, it copies rules to both 80 and 443 ports
Steps to reproduce
✗ k get ingress <redacted> -o yaml
apiVersion: networking.k8s.io/v1 kind: Ingress metadata: annotations: alb.ingress.kubernetes.io/actions.ssl-redirect: "443" alb.ingress.kubernetes.io/certificate-arn: arn:aws:acm:us-east-1:<redacted>:certificate/<redacted> alb.ingress.kubernetes.io/listen-ports: '[{"HTTPS": 443},{"HTTP": 80}]' alb.ingress.kubernetes.io/scheme: internet-facing external-dns.alpha.kubernetes.io/hostname: <redacted> kubernetes.io/ingress.class: alb creationTimestamp: "2023-06-22T14:51:27Z" finalizers: - ingress.k8s.aws/resources generation: 4 name: <redacted> namespace: default resourceVersion: "<redacted>" uid: <redacted> spec: rules: - http: paths: - backend: service: name: <redacted> port: number: 4141 path: /* pathType: ImplementationSpecific status: loadBalancer: ingress: - hostname: <redacted>
Expected outcome An ssl redirect from port 80 to 443 should be shown as a default and only rule.
All the rules should be in the 443 listener.
Environment
2.4.6
1.23
Additional Context:
Looks like I had an incorrect annotation
- alb.ingress.kubernetes.io/actions.ssl-redirect: "443" + alb.ingress.kubernetes.io/ssl-redirect: '443'
Describe the bug The ssl-redirect doesn't add a target group redirect. Instead, it copies rules to both 80 and 443 ports
Steps to reproduce
Expected outcome An ssl redirect from port 80 to 443 should be shown as a default and only rule.
All the rules should be in the 443 listener.
Environment
2.4.6
- This is out of date and may be the culprit1.23
1.23
Additional Context: