<p>I'm fairly new to Kubernetes, and I am trying to get SEQ up and running in im the environment. Everything looks like its provisioned correctly, but I can not seem to hit the endpoint. Chrome just spins and eventually says <code>ERR_CONNECTION_TIMED_OUT</code>.</p>

<p>I tried another example from <a href="https://github.com/Azure-Samples/azure-voting-app-redis/blob/master/azure-vote-all-in-one-redis.yaml" rel="nofollow noreferrer">microsoft</a> and it works correctly. I can hit it from the outside world.</p>

<p>Here is my yaml file:</p>

<pre><code>kind: Pod
apiVersion: v1
metadata:
  name: seq
spec:
  replicas: 1
  containers:
  - name: seq
    image: datalust/seq:latest
    ports:
    - containerPort: 80
    - containerPort: 5341
    env:
    - name: ACCEPT_EULA
      value: "Y"
    volumeMounts:
    - mountPath: "/data"
      name: volume
  volumes:
    - name: volume
      persistentVolumeClaim:
        claimName: azure-managed-disk
---
apiVersion: v1
kind: Service
metadata:
  name: seq
spec:
  type: LoadBalancer
  ports:
  - port: 80
  selector:
    app: seq    
</code></pre>

<p><a href="https://i.stack.imgur.com/GgPTl.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/GgPTl.png" alt="enter image description here"></a>
<a href="https://i.stack.imgur.com/g3PYB.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/g3PYB.png" alt="enter image description here"></a></p>

Chris Kooken
<p>It looks like that your Pod manifest is missing the following in the <code>metadata</code> section:</p>

<pre><code>labels:
    app: seq
</code></pre>

<p>It should match what's defined in the Service <code>selector</code> section. That's what glues the Service and Pod objects together.</p>

<p>By the way, the statement <code>replicas: 1</code> is not part of a Pod manifest but instead used in Deployments to specify how many Pods should be created initially.</p>

<p>To further explain a bit on the topic on how Deployments and Pods usually relates to each other, maybe my answer <a href="https://stackoverflow.com/questions/51857582/which-names-should-be-same-in-this-k8s-yaml/51865961#51865961">here</a>, could be a good reference. The same logic applies on how Services and Pods relates to each other and <code>labels</code> is an important part of that.</p>
