HttpListener is created for http when http is disabled

[azure]

HttpListener is created for http when http is disabled

[robertprather]

I support all previous comments on this thread and would like to see this implemented ASAP.

Using the application gateway to enable the HTTPS listener and perform SSL offload to the K8S cluster is working great, but leaving the HTTP listener enabled is causing us grief with our security team. We want the ingress controller to update the gateway and set the desired state without manual updates.

An annotation would work, suggest 2 possible ones:

1. ssl-require: if this annotation is present, would disable the HTTP listener if HTTPS is specified in the ingress
2. ssl-redirect: if this annotation is present, would keep both the HTTP and HTTPS listeners present on the gateway, but apply a redirect rule for HTTP -> HTTPS (k8s--80-rr rule would redirect k8s--80-fl listener to k8s--443-fl listener)

[asridharan]

Fixed by #120

[asridharan]

@wesselkranenborg make sense. Just to clarify, you want the HTTP listener to be disabled if we specify only HTTPS in the ingress right?

[wesselkranenborg]

That is indeed what we want.

[dan-jackson-github]

@asridharan can you indicate when the annotation support for disabling HTTP access will be available? Creating an HTTP endpoint by default really isn't ideal and means more manual work to do remember after deployment

[asridharan]

@wesselkranenborg @robertprather have a partial fix for this problem in
#120

Its partial since even after this PR we won't have support for SSL-redirect on HTTP listeners. Will work on that after this PR. Wanted to check if it would help resolve this issue?

[asridharan]

@wesselkranenborg @dan-jackson-github @robertprather can you try helm chart 0.3.0 which has the fix for this issue?

Thanks,
Avinash

[robertprather]

I've tried helm chart 0.3.0 and it works as expected - no http listener created. Rob