<p>Hey guys i have a django rest application and every time that i expose the deployment with service, my minikube doesn't expose the IP, anyone knows how to solved it? I wait 3 hours and my minikube doesn't show any IP.</p>

<p>Pod/container log:</p>

<pre><code>&amp;lt;django.db.models.fields.related.ForeignKey&amp;gt;
&amp;lt;django.db.models.fields.TextField&amp;gt;
&amp;lt;django.db.models.fields.related.ForeignKey&amp;gt;
Operations to perform:
  Apply all migrations: admin, auth, authtoken, chat, contenttypes, notifications, sessions
Running migrations:
  No migrations to apply.
&amp;lt;django.db.models.fields.related.ForeignKey&amp;gt;
&amp;lt;django.db.models.fields.TextField&amp;gt;
&amp;lt;django.db.models.fields.related.ForeignKey&amp;gt;
&amp;lt;django.db.models.fields.related.ForeignKey&amp;gt;
&amp;lt;django.db.models.fields.TextField&amp;gt;
&amp;lt;django.db.models.fields.related.ForeignKey&amp;gt;
Performing system checks...
 System check identified no issues (0 silenced).
August 06, 2018 - 19:14:37
Django version 2.0.1, using settings 'chatire.settings'
Starting development server at http://0.0.0.0:8000/
Quit the server with CONTROL-C
</code></pre>

<p>backend-service:</p>

<pre><code>apiVersion: v1
kind: Service
metadata:
  name: backend-service
spec:
  type: NodePort
  ports:
    - port: 8000
      nodePort: 30001
  selector:
    service: backend-pod
</code></pre>

<p>backend-deployment:</p>

<pre><code>apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: backend-deployment
spec:
  template:
    metadata:
      labels:
       name: backend-pod
    spec:
      containers:
        - name: container-backend
          image: modalgr.azurecr.io/chatbot/backend:v1.1
          ports:
          - containerPort: 8000
          command: ["/bin/sh"]
          args: ["app.sh"]
      restartPolicy: Always
      imagePullSecrets:
      - name: azure-auth
</code></pre>

<p>Error log:</p>

<pre><code>C:\Users\Youssef\Documents\kubernetes&gt;minikube service backend-service | findstr IP
Waiting, endpoint for service is not ready yet...
Waiting, endpoint for service is not ready yet...
Waiting, endpoint for service is not ready yet...
Waiting, endpoint for service is not ready yet...
</code></pre>

Daniel Pereira
<p>The error <code>Waiting, endpoint for service is not ready yet...</code> means that your Service can’t find your Pod. </p>

<p>It happens because the label name in Service does not match the  label name in Deployment.</p>

<p>To fix this issue you should change  <code>name: backend-pod</code> to <code>service: backend-pod</code> in Deployment.</p>
