<p>I have the following service/deployment where I the docker image just responds to requests on port 80 with &quot;hello world&quot;</p>
<pre><code>apiVersion: apps/v1
kind: Deployment
metadata:
  name: test
spec:
  replicas: 1
  selector:
    matchLabels:
      app: test
  template:
    metadata:
      labels:
        app: test
    spec:
      containers:
        - name: helloworld
          image: */helloworld:latest
          ports:
          - containerPort: 80
          resources:
            limits:
              cpu: &quot;250m&quot;
              memory: &quot;1Gi&quot;
---
apiVersion: v1
kind: Service
metadata:
  name: test
spec:
  type: LoadBalancer
  selector:
    app: test
  ports:
  - port: 80
    targetPort: 80
    protocol: TCP
  externalIPs:
  - 192.168.0.10
status:
  loadBalancer: {}
</code></pre>
<p>I'm expecting to be able to connect to 192.168.0.10:80, but I get &quot;took too long to respond&quot;</p>
<p>I can verify the service is running with <code>minikube kubectl get services</code> which gives me</p>
<p><code>test         LoadBalancer   10.97.157.242    192.168.0.10   80:31912/TCP     48m</code></p>
<p>and the pod the service points to is started. <code>minikube kubectl get pods</code> gives me</p>
<p><code>test-55c8cc69b5-h7xj6       1/1     Running       0             11s</code></p>

Gunslinger
<p>From the <a href="https://minikube.sigs.k8s.io/docs/handbook/accessing/#loadbalancer-access" rel="nofollow noreferrer">docs</a>:</p>
<blockquote>
<p>Services of type <code>LoadBalancer</code> can be exposed via the <code>minikube tunnel</code>
command. It must be run in a separate terminal window to keep the
<code>LoadBalancer</code> running.</p>
</blockquote>
<p>Running <code>minikube tunnel</code> in a separate terminal should make your Service accessible.</p>
