Disable HTTPS Redirect for NGINX Ingress

Rancher 2.x
1

An SSL redirect is enabled by default in a Kubernetes NGINX ingress. How can this be disabled?
In the rancher GUI i have created a Load Balancer with the annotations.

nginx.ingress.kubernetes.io/ssl-redirect: ‘false’

Bit if i open the url in chrome or firefox and add http:// the url is redirected to https://

Does anyone have an idea what is wrong?

Current implementation below:

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
annotations:
field.cattle.io/creatorId: u-3jglkiqgjx
field.cattle.io/ingressState: ‘{“ZGFydGVzdDA2LmxueC5hczI0LmRldi9kYXItdGVzdHMvZGFydGVzdDA2LmxueC5hczI0LmRldi8vLzgw”:“deployment:dar-tests:nginxport80”}’
field.cattle.io/publicEndpoints: ‘[{“addresses”:[“81.203.253.65”],“port”:80,“protocol”:“HTTP”,“serviceName”:“dar-tests:ingress-0de29cdf772974f51f9336d60721da09”,“ingressName”:“dar-tests:dartest06.mydomain.com”,“hostname”:“dartest06.mydomain.com”,“path”:“/”,“allNodes”:true}]’
nginx.ingress.kubernetes.io/ssl-redirect: ‘false’
creationTimestamp: “2020-03-11T09:18:11Z”
generation: 1
labels:
cattle.io/creator: norman
name: dartest06.mydomain.com
namespace: dar-tests
resourceVersion: “13943544”
selfLink: /apis/extensions/v1beta1/namespaces/dar-tests/ingresses/dartest06.mydomain.com
uid: ee9a8f8b-320c-44f2-ae5c-f1365ac4ae4b
spec:
rules:
-host: dartest06.mydomain.com
http:
paths:
- backend:
serviceName: ingress-0de29cdf772974f51f9336d60721da09
servicePort: 80
path: /
status:
loadBalancer:
ingress:
- ip: 81.203.253.65
- ip: 81.203.253.66
- ip: 81.203.253.67

2

Besides the annotation you have added:
nginx.ingress.kubernetes.io/ssl-redirect: ‘false’,
you should also supply another one:
nginx.ingress.kubernetes.io/force-ssl-redirect: ‘false’
It really works.

3

Even after adding those two annotation
nginx.ingress.kubernetes.io/ssl-redirect:‘false’
nginx.ingress.kubernetes.io/force-ssl-redirect:‘false’
Doesn’t work for me?

4

Make sure that not the browser already does that for you due to HSTS [1]

[1] HTTP Strict Transport Security – Wikipedia

5

Do you have an Load balancer in front of the cluster? If so, have you checked the settings there?

And as @bpedersen2 - depending on the domain, it might have HSTS, or your browser just have cached it.