<p>I am using  the concourse helm build provided at <a href="https://github.com/kubernetes/charts/tree/master/stable/concourse" rel="nofollow noreferrer">https://github.com/kubernetes/charts/tree/master/stable/concourse</a> to setup concourse inside of our kubernetes cluster. I have been able to get the setup working and I am able to access it within the cluster but I am having trouble accessing it outside the cluster. The notes from the build show that I can just use <code>kubectl port-forward</code> to get to the webpage but I don't want to have all of the developers have to forward the port just to get to the web ui. I have tried creating a service that has a node port like this:</p>

<pre><code>apiVersion: v1
kind: Service
metadata:
  name: concourse
  namespace: concourse-ci
spec:
  ports:
  - port: 8080
    name: atc
    nodePort: 31080
  - port: 2222
    name: tsa
    nodePort: 31222
  selector:
    app: concourse-web
  type: NodePort
</code></pre>

<p>This allows me to get to the webpage and interact with it in most ways but then when I try to look at build status it never loads the events that happened. Instead a network request for <code>/api/v1/builds/1/events</code> is stuck in pending and the steps of the build never load. Any ideas what I can do to be able to completely access concourse external to the cluster?</p>

<p>EDIT: It seems like the events network request normally responds with a <code>text/event-stream</code> data type and maybe the Kubernetes service isn't handling an event stream correctly. Or there is something about concourse that handles event-streams different than the norm.</p>

<p>After plenty of investigation I have found that the the nodePort service is actually working and it is just my antivirus (Sophos) that is silently blocking the response from the <code>events</code> request.</p>
