Ingress controller not supporting Server-Sent Events - zero documentation to help with this.

[martinmclarnon]

What happened:

What you expected to happen:

NGINX Ingress controller version (exec into the pod and run nginx-ingress-controller --version.):

Kubernetes version (use kubectl version):

Environment:

• Cloud provider or hardware configuration:

• OS (e.g. from /etc/os-release):

• Kernel (e.g. uname -a):

• Install tools:

  • Please mention how/where was the cluster created like kubeadm/kops/minikube/kind etc.

• Basic cluster related info:

  • kubectl version
  • kubectl get nodes -o wide

• How was the ingress-nginx-controller installed:

  • If helm was used then please show output of helm ls -A | grep -i ingress
  • If helm was used then please show output of helm -n <ingresscontrollernamepspace> get values <helmreleasename>
  • If helm was not used, then copy/paste the complete precise command used to install the controller, along with the flags and options used
  • if you have more than one instance of the ingress-nginx-controller installed in the same cluster, please provide details for all the instances

• Current State of the controller:

  • kubectl describe ingressclasses
  • kubectl -n <ingresscontrollernamespace> get all -A -o wide
  • kubectl -n <ingresscontrollernamespace> describe po <ingresscontrollerpodname>
  • kubectl -n <ingresscontrollernamespace> describe svc <ingresscontrollerservicename>

• Current state of ingress object, if applicable:

  • kubectl -n <appnnamespace> get all,ing -o wide
  • kubectl -n <appnamespace> describe ing <ingressname>
  • If applicable, then, your complete and exact curl/grpcurl command (redacted if required) and the reponse to the curl/grpcurl command with the -v flag

• Others:

  • Any other related information like ;
    • copy/paste of the snippet (if applicable)
    • kubectl describe ... of any custom configmap(s) created and in use
    • Any other related information that may help

How to reproduce this issue:

Anything else we need to know:

Frontend Angular application calls a Server-Sent Event. This works until the application is served via an Ingress Controller. There is zero documentation to aid with the correct list of annotations to make this work. There is a reference on this site to a change to the code to add an annotation "eventsource" that is binary but this is not included in the list of acceptable annotations. This is preventing the release to a client and I need to get this working. Any help is greatly appreciated.

[k8s-ci-robot]

This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

[longwuyuan]

/remove-kind bug

There are less people here for this but you may get useful comments on kubernetes.slack in the ingress-nginx-users channel. Signup at slack.k8s.io if required.

Also if this turns out to be a bug or a new-feature, the description is better with answers to the questions asked in the template.

Actually if you can paste a link to what exactly is server-sent event, it may throw more light on the context with HTTP/HTTPS protocol specs and thus relate more directly to ingress. Generall for things like websockets or headers, the controller works out of the box. So the error message in the controller pod logs could point to something that relates directly between server-sent event and HTTP/HTTPS via the controller.

[toredash]

@martinmclarnon

Would you mind creating a doc PR for this ? Using this as a reference should aid you with a Ingress object that should work:
https://serverfault.com/questions/801628/for-server-sent-events-sse-what-nginx-proxy-configuration-is-appropriate

[longwuyuan]

/triage needs-information

[martinmclarnon]

Thank you for all inputs. It turns out a rather vital piece of data had been left out of the DB and after discovering this the frontend worked. The issue had nothing to do with the Ingress nor SSE.

[toredash]

@martinmclarnon would you mind closing the issue of the issue is resolved?

[longwuyuan]

/close

[k8s-ci-robot]

@longwuyuan: Closing this issue.

In response to this:

/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.