<p>I have a simple Webserver that exposes the pod name on which it is located by using the <code>OUT</code> env var.</p>
<p>Deployment and service look like this:</p>
<pre class="lang-yaml prettyprint-override"><code>apiVersion: v1
kind: Service
metadata:
  name: simpleweb-service
spec:
  selector:
    app: simpleweb
  ports:
    - protocol: TCP
      port: 8080
      targetPort: 8080
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: simpleweb-deployment
  labels:
    app: simpleweb
spec:
  replicas: 3
  selector:
    matchLabels:
      app: simpleweb
  template:
    metadata:
      labels:
        app: simpleweb
    spec:
      containers:
      - name: simpleweb
        env:
          - name: OUT
            valueFrom:
              fieldRef:
                fieldPath: metadata.name
        imagePullPolicy: Never
        image: simpleweb
        ports:
        - containerPort: 8080
</code></pre>
<p>I deploy this on my local <a href="https://kind.sigs.k8s.io" rel="nofollow noreferrer">kind cluster</a></p>
<pre><code>default   simpleweb-deployment-5465f84584-m59n5 1/1     Running   0   12m
default   simpleweb-deployment-5465f84584-mw8vj 1/1     Running   0   9m36s
default   simpleweb-deployment-5465f84584-x6n74 1/1     Running   0   12m
</code></pre>
<p>and access it via</p>
<pre class="lang-bash prettyprint-override"><code>kubectl port-forward service/simpleweb-service 8080:8080
</code></pre>
<p>When I am hitting <code>localhost:8080</code> I always get to the same pod</p>
<p><strong>Questions:</strong></p>
<ul>
<li>Is my service not doing round robin?</li>
<li>Is there some caching that I am not aware of</li>
<li>Do I have to expose my service differently? Is this a kind issue?</li>
</ul>

User12547645
<p>To do round-robin and route to different services I have to use a <code>LoadBalancer</code> service. There is <a href="https://kind.sigs.k8s.io/docs/user/loadbalancer/" rel="nofollow noreferrer">MetalLB</a> that implements a LB for Kind. Unfortunately it currently <a href="https://github.com/kubernetes-sigs/kind/issues/1961#issuecomment-912922550" rel="nofollow noreferrer">does not support Apply M1 machines</a>.</p>
<p>I assume that MetallLB + LoadBalancer Service would work on a different machine.</p>
